Re: [Gluster-users] High load on glusterfsd process

[Pranith Kumar Karampuri <pkarampu@xxxxxxxxxx>]

+Kotresh who seems to have worked on the bug you mentioned.

On Fri, Apr 21, 2017 at 12:21 PM, ABHISHEK PALIWAL <abhishpaliwal@xxxxxxxxx> wrote:

If the patch provided in that case will resolve my bug as well then please provide the patch so that I will backport it on 3.7.6

On Fri, Apr 21, 2017 at 11:30 AM, ABHISHEK PALIWAL <abhishpaliwal@xxxxxxxxx> wrote:

Hi Team,

I have noticed that there are so many glusterfsd threads are running in my system and we observed some of those thread consuming more cpu. I did “strace” on two such threads (before the problem disappeared by itself) and found that there is a continuous activity like below:

lstat("/opt/lvmdir/c2/brick/.glusterfs/e7/7d/e77d12b3-92f8-4dfe-9a7f-246e901cbdf1/002700/firewall_-J208482-4000025_20170126T113552+0000.log.gz", {st_mode=S_IFREG|0670, st_size=1995, ...}) = 0
lgetxattr("/opt/lvmdir/c2/brick/.glusterfs/e7/7d/e77d12b3-92f8-4dfe-9a7f-246e901cbdf1/002700/firewall_-J208482-4000025_20170126T113552+0000.log.gz", "trusted.bit-rot.bad-file", 0x3fff81f58550, 255) = -1 ENODATA (No data available)
lgetxattr("/opt/lvmdir/c2/brick/.glusterfs/e7/7d/e77d12b3-92f8-4dfe-9a7f-246e901cbdf1/002700/firewall_-J208482-4000025_20170126T113552+0000.log.gz", "trusted.bit-rot.signature", 0x3fff81f58550, 255) = -1 ENODATA (No data available)
lstat("/opt/lvmdir/c2/brick/.glusterfs/e7/7d/e77d12b3-92f8-4dfe-9a7f-246e901cbdf1/002700/tcli_-J208482-4000025_20170123T180550+0000.log.gz", {st_mode=S_IFREG|0670, st_size=169, ...}) = 0
lgetxattr("/opt/lvmdir/c2/brick/.glusterfs/e7/7d/e77d12b3-92f8-4dfe-9a7f-246e901cbdf1/002700/tcli_-J208482-4000025_20170123T180550+0000.log.gz", "trusted.bit-rot.bad-file", 0x3fff81f58550, 255) = -1 ENODATA (No data available)
lgetxattr("/opt/lvmdir/c2/brick/.glusterfs/e7/7d/e77d12b3-92f8-4dfe-9a7f-246e901cbdf1/002700/tcli_-J208482-4000025_20170123T180550+0000.log.gz", "trusted.bit-rot.signature", 0x3fff81f58550, 255) = -1 ENODATA (No data available)

I have found the below existing issue which is very similar to my scenario.

https://bugzilla.redhat.com/show_bug.cgi?id=1298258

We are using the gluster-3.7.6 and it seems that the issue is fixed in 3.8.4 version.

Could you please let me know why it showing the number of above logs and reason behind it as it is not explained in the above bug.

Regards,

Abhishek

--

Regards
Abhishek Paliwal

--

Regards
Abhishek Paliwal

_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-users

--

Pranith

_______________________________________________
Gluster-devel mailing list
Gluster-devel@xxxxxxxxxxx
http://lists.gluster.org/mailman/listinfo/gluster-devel