[Bugs] [Bug 1427390] systemic testing: seeing lot of ping time outs which would lead to splitbrains
bugzilla at redhat.com
bugzilla at redhat.com
Wed Mar 1 08:47:43 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1427390
--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16777 committed in release-3.8 by Niels de
Vos (ndevos at redhat.com)
------
commit f9aaa26332ba7007265967bc29a1a2a99234a26d
Author: Krutika Dhananjay <kdhananj at redhat.com>
Date: Mon Jan 23 17:40:40 2017 +0530
storage/posix: Execute syscalls in xattrop under different locks
Backport of: https://review.gluster.org/16462 and
https://review.gluster.org/16792
... and not inode->lock. This is to prevent the epoll thread from
*potentially* being blocked on this lock in the worst case for
extended period elsewhere in the brick stack, while the syscalls
in xattrop are being performed under the same lock by a different
thread. This could potentially lead to ping-timeout, if the only
available epoll thread is busy waiting on the inode->lock, thereby
preventing it from picking up the ping request from the client(s).
Also removed some unused functions.
>Change-Id: I2054a06701ecab11aed1c04e80ee57bbe2e52564
>BUG: 1421938
>Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
>Reviewed-on: https://review.gluster.org/16462
>Smoke: Gluster Build System <jenkins at build.gluster.org>
>NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
>Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
>CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
(cherry picked from commit b5c26a462caf97bfc5380c81092f5c331ccaf1ae)
Change-Id: I2054a06701ecab11aed1c04e80ee57bbe2e52564
BUG: 1427390
Signed-off-by: Krutika Dhananjay <kdhananj at redhat.com>
Reviewed-on: https://review.gluster.org/16777
Smoke: Gluster Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
Reviewed-by: Raghavendra G <rgowdapp at redhat.com>
Reviewed-by: Niels de Vos <ndevos at redhat.com>
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list