<div>Quite helpful, I definitely feel this to be a good blog material.</div><div><br><div class="gmail_quote"><div>On Thu, 12 Jan 2017 at 16:29, Raghavendra Gowdappa &lt;<a href="mailto:rgowdapp@redhat.com">rgowdapp@redhat.com</a>&gt; wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">All,<br class="gmail_msg"><br><br class="gmail_msg"><br>Not sure many of us know about how to selectively set log-level of an xlator. Thought this might be helpful to someone.<br class="gmail_msg"><br><br class="gmail_msg"><br>To selectively set log-level of an xlator we need to do setfattr on any path in glusterfs with &quot;trusted.glusterfs.%s.set-log-level&quot; (where %s is name of xlator in xlator graph) as key and log-level as value. For eg.,<br class="gmail_msg"><br><br class="gmail_msg"><br>[root@unused glusterfs]# gluster volume info<br class="gmail_msg"><br><br class="gmail_msg"><br>Volume Name: r2<br class="gmail_msg"><br>Type: Distributed-Replicate<br class="gmail_msg"><br>Volume ID: ff216e89-23a0-4b1e-9cf6-5f3bceea68bf<br class="gmail_msg"><br>Status: Started<br class="gmail_msg"><br>Snapshot Count: 0<br class="gmail_msg"><br>Number of Bricks: 2 x 2 = 4<br class="gmail_msg"><br>Transport-type: tcp<br class="gmail_msg"><br>Bricks:<br class="gmail_msg"><br>Brick1: localhost.localdomain:/home/gfs/r2_0<br class="gmail_msg"><br>Brick2: localhost.localdomain:/home/gfs/r2_1<br class="gmail_msg"><br>Brick3: localhost.localdomain:/home/gfs/r2_2<br class="gmail_msg"><br>Brick4: localhost.localdomain:/home/gfs/r2_3<br class="gmail_msg"><br>Options Reconfigured:<br class="gmail_msg"><br>nfs.disable: on<br class="gmail_msg"><br>performance.readdir-ahead: on<br class="gmail_msg"><br>transport.address-family: inet<br class="gmail_msg"><br><br class="gmail_msg"><br>For the above volume the client translators are named as,<br class="gmail_msg"><br>r2-client-0<br class="gmail_msg"><br>r2-client-1<br class="gmail_msg"><br>r2-client-2<br class="gmail_msg"><br>r2-client-3<br class="gmail_msg"><br><br class="gmail_msg"><br>To set log-level<br class="gmail_msg"><br><br class="gmail_msg"><br>[root@unused glusterfs]# mount<br class="gmail_msg"><br>booradley:/r2 on /mnt/glusterfs type fuse.glusterfs (rw,relatime,user_id=0,group_id=0,default_permissions,allow_other,max_read=131072)<br class="gmail_msg"><br><br class="gmail_msg"><br>[root@unused rhs-glusterfs]# cd /mnt/glusterfs<br class="gmail_msg"><br>[root@unused glusterfs]# pwd<br class="gmail_msg"><br>/mnt/glusterfs<br class="gmail_msg"><br><br class="gmail_msg"><br>[root@unused glusterfs]# setfattr . -n &quot;trusted.glusterfs.r2-client-0.set-log-level&quot; -v TRACE<br class="gmail_msg"><br>[root@unused glusterfs]# setfattr . -n &quot;trusted.glusterfs.r2-client-1.set-log-level&quot; -v TRACE<br class="gmail_msg"><br>[root@unused glusterfs]# setfattr . -n &quot;trusted.glusterfs.r2-client-2.set-log-level&quot; -v TRACE<br class="gmail_msg"><br>[root@unused glusterfs]# setfattr . -n &quot;trusted.glusterfs.r2-client-3.set-log-level&quot; -v TRACE<br class="gmail_msg"><br><br class="gmail_msg"><br>Note that this feature is available only for clients/fuse-mount process as of now. Other daemons (bricks, selfheald, rebalance etc) don&#39;t have this feature.<br class="gmail_msg"><br><br class="gmail_msg"><br>regards,<br class="gmail_msg"><br>Raghavendra<br class="gmail_msg"><br>_______________________________________________<br class="gmail_msg"><br>Gluster-devel mailing list<br class="gmail_msg"><br><a href="mailto:Gluster-devel@gluster.org" class="gmail_msg" target="_blank">Gluster-devel@gluster.org</a><br class="gmail_msg"><br><a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" class="gmail_msg" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-devel</a><br class="gmail_msg"><br></blockquote></div></div><div dir="ltr">-- <br></div><div data-smartmail="gmail_signature">- Atin (atinm)</div>