<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 07/27/2016 04:33 PM, Raghavendra G
wrote:<br>
</div>
<blockquote
cite="mid:CADRNtgSzBBsWP16BVPdcdaqLRkjT8RcfubfDqb-B4M6qKCgOwA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Jul 27, 2016 at 10:29 AM,
Mohammed Rafi K C <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:rkavunga@redhat.com"
target="_blank"><a class="moz-txt-link-abbreviated" href="mailto:rkavunga@redhat.com">rkavunga@redhat.com</a></a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Thanks for your feedback.</p>
<p>In fact meta xlator is loaded only on fuse mount, is
there any particular reason to not to use
meta-autoload xltor for nfs server and libgfapi ?</p>
</div>
</blockquote>
<div><br>
</div>
<div style="">I think its because of lack of resources. I am
not aware of any technical reason for not using on NFSv3
server and gfapi.</div>
</div>
</div>
</div>
</blockquote>
<br>
Cool. I will try to see how we can implement meta-autoliad feature
for nfs-server and libgfapi. Once we have the feature in place, I
will implement the cache memory display/flush feature using meta
xlators.<br>
<br>
Thanks for your valuable feedback.<br>
Rafi KC<br>
<br>
<blockquote
cite="mid:CADRNtgSzBBsWP16BVPdcdaqLRkjT8RcfubfDqb-B4M6qKCgOwA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div style=""> <br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p>Regards</p>
<p>Rafi KC<br>
</p>
<div>
<div class="h5">
<div>On 07/26/2016 04:05 PM, Niels de Vos wrote:<br>
</div>
<blockquote type="cite">
<pre>On Tue, Jul 26, 2016 at 12:43:56PM +0530, Kaushal M wrote:
</pre>
<blockquote type="cite">
<pre>On Tue, Jul 26, 2016 at 12:28 PM, Prashanth Pai <a moz-do-not-send="true" href="mailto:ppai@redhat.com" target="_blank"><ppai@redhat.com></a> wrote:
</pre>
<blockquote type="cite">
<pre>+1 to option (2) which similar to echoing into /proc/sys/vm/drop_caches
-Prashanth Pai
----- Original Message -----
</pre>
<blockquote type="cite">
<pre>From: "Mohammed Rafi K C" <a moz-do-not-send="true" href="mailto:rkavunga@redhat.com" target="_blank"><rkavunga@redhat.com></a>
To: "gluster-users" <a moz-do-not-send="true" href="mailto:gluster-users@gluster.org" target="_blank"><gluster-users@gluster.org></a>, "Gluster Devel" <a moz-do-not-send="true" href="mailto:gluster-devel@gluster.org" target="_blank"><gluster-devel@gluster.org></a>
Sent: Tuesday, 26 July, 2016 10:44:15 AM
Subject: [Gluster-devel] Need a way to display and flush gluster cache ?
Hi,
Gluster stack has it's own caching mechanism , mostly on client side.
But there is no concrete method to see how much memory are consuming by
gluster for caching and if needed there is no way to flush the cache memory.
So my first question is, Do we require to implement this two features
for gluster cache?
If so I would like to discuss some of our thoughts towards it.
(If you are not interested in implementation discussion, you can skip
this part :)
1) Implement a virtual xattr on root, and on doing setxattr, flush all
the cache, and for getxattr we can print the aggregated cache size.
2) Currently in gluster native client support .meta virtual directory to
get meta data information as analogues to proc. we can implement a
virtual file inside the .meta directory to read the cache size. Also we
can flush the cache using a special write into the file, (similar to
echoing into proc file) . This approach may be difficult to implement in
other clients.
</pre>
</blockquote>
</blockquote>
<pre>+1 for making use of the meta-xlator. We should be making more use of it.
</pre>
</blockquote>
<pre>Indeed, this would be nice. Maybe this can also expose the memory
allocations like /proc/slabinfo.
The io-stats xlator can dump some statistics to
/var/log/glusterfs/samples/ and /var/lib/glusterd/stats/ . That seems to
be acceptible too, and allows to get statistics from server-side
processes without involving any clients.
HTH,
Niels
</pre>
<blockquote type="cite">
<blockquote type="cite">
<blockquote type="cite">
<pre>3) A cli command to display and flush the data with ip and port as an
argument. GlusterD need to send the op to client from the connected
client list. But this approach would be difficult to implement for
libgfapi based clients. For me, it doesn't seems to be a good option.
Your suggestions and comments are most welcome.
Thanks to Talur and Poornima for their suggestions.
Regards
Rafi KC
_______________________________________________
Gluster-devel mailing list
<a moz-do-not-send="true" href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a>
<a moz-do-not-send="true" href="http://www.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a>
</pre>
</blockquote>
<pre>_______________________________________________
Gluster-devel mailing list
<a moz-do-not-send="true" href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a>
<a moz-do-not-send="true" href="http://www.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a>
</pre>
</blockquote>
<pre>_______________________________________________
Gluster-users mailing list
<a moz-do-not-send="true" href="mailto:Gluster-users@gluster.org" target="_blank">Gluster-users@gluster.org</a>
<a moz-do-not-send="true" href="http://www.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a>
</pre>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Gluster-devel mailing list
<a moz-do-not-send="true" href="mailto:Gluster-devel@gluster.org" target="_blank">Gluster-devel@gluster.org</a>
<a moz-do-not-send="true" href="http://www.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a></pre>
</blockquote>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Gluster-devel mailing list<br>
<a moz-do-not-send="true"
href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a moz-do-not-send="true"
href="http://www.gluster.org/mailman/listinfo/gluster-devel"
rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div class="gmail_signature" data-smartmail="gmail_signature">Raghavendra
G<br>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>