Bug 1427390
Summary: | systemic testing: seeing lot of ping time outs which would lead to splitbrains | ||
---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Raghavendra G <rgowdapp> |
Component: | rpc | Assignee: | Raghavendra G <rgowdapp> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | |
Severity: | urgent | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.8 | CC: | bugs, kdhananj, mchangir, moagrawa, nchilaka, rcyriac, rgowdapp, rhinduja, rhs-bugs |
Target Milestone: | --- | Keywords: | Reopened, Triaged |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | rpc-ping-timeout | ||
Fixed In Version: | glusterfs-3.8.11 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | 1421938 | Environment: | |
Last Closed: | 2017-04-11 09:06:50 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1421938 | ||
Bug Blocks: | 1415178, 1431410 |
Description
Raghavendra G
2017-02-28 04:45:02 UTC
REVIEW: https://review.gluster.org/16777 (storage/posix: Execute syscalls in xattrop under different locks) posted (#1) for review on release-3.8 by Raghavendra G (rgowdapp) REVIEW: https://review.gluster.org/16777 (storage/posix: Execute syscalls in xattrop under different locks) posted (#2) for review on release-3.8 by Krutika Dhananjay (kdhananj) COMMIT: https://review.gluster.org/16777 committed in release-3.8 by Niels de Vos (ndevos) ------ commit f9aaa26332ba7007265967bc29a1a2a99234a26d Author: Krutika Dhananjay <kdhananj> 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> >Reviewed-on: https://review.gluster.org/16462 >Smoke: Gluster Build System <jenkins.org> >NetBSD-regression: NetBSD Build System <jenkins.org> >Reviewed-by: Raghavendra G <rgowdapp> >CentOS-regression: Gluster Build System <jenkins.org> (cherry picked from commit b5c26a462caf97bfc5380c81092f5c331ccaf1ae) Change-Id: I2054a06701ecab11aed1c04e80ee57bbe2e52564 BUG: 1427390 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: https://review.gluster.org/16777 Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp> Reviewed-by: Niels de Vos <ndevos> REVIEW: https://review.gluster.org/16892 (storage/posix: Use more granular mutex locks for atomic writes) posted (#1) for review on release-3.8 by Krutika Dhananjay (kdhananj) REVIEW: https://review.gluster.org/16893 (storage/posix: Use granular mutex locks for pgfid update syscalls) posted (#1) for review on release-3.8 by Krutika Dhananjay (kdhananj) This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.10, please open a new bug report. glusterfs-3.8.10 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/announce/2017-March/000068.html [2] https://www.gluster.org/pipermail/gluster-users/ COMMIT: https://review.gluster.org/16892 committed in release-3.8 by jiffin tony Thottan (jthottan) ------ commit 5e1324fffebbf6a650d6aff33849a8362300c1cc Author: Krutika Dhananjay <kdhananj> Date: Tue Feb 28 14:27:51 2017 +0530 storage/posix: Use more granular mutex locks for atomic writes Backport of: https://review.gluster.org/16785 Change-Id: I64aa561cb76ff9d4597d91fb5aeb64531698936a BUG: 1427390 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: https://review.gluster.org/16892 NetBSD-regression: NetBSD Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu> Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> REVIEW: https://review.gluster.org/16893 (storage/posix: Use granular mutex locks for pgfid update syscalls) posted (#2) for review on release-3.8 by Krutika Dhananjay (kdhananj) COMMIT: https://review.gluster.org/16893 committed in release-3.8 by jiffin tony Thottan (jthottan) ------ commit 8b8098ed5c6e0f5a82d89c9d5f22bd7b17d6a882 Author: Krutika Dhananjay <kdhananj> Date: Tue Feb 28 15:52:49 2017 +0530 storage/posix: Use granular mutex locks for pgfid update syscalls Backport of: https://review.gluster.org/16869 Change-Id: I5c48b3be3f39bb8f951d33e2729522605384d1ff BUG: 1427390 Signed-off-by: Krutika Dhananjay <kdhananj> Reviewed-on: https://review.gluster.org/16893 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Pranith Kumar Karampuri <pkarampu> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.8.11, please open a new bug report. glusterfs-3.8.11 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/packaging/2017-April/000289.html [2] https://www.gluster.org/pipermail/gluster-users/ |