Bug 1522968 - glusterd bug fixes
Summary: glusterd bug fixes
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: glusterd
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-06 20:46 UTC by siri uppalapati
Modified: 2018-03-15 11:23 UTC (History)
2 users (show)

Fixed In Version: glusterfs-4.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-15 11:23:27 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description siri uppalapati 2017-12-06 20:46:34 UTC
bug fixes in management daemon

Comment 1 Worker Ant 2017-12-06 20:49:13 UTC
REVIEW: https://review.gluster.org/18974 (Fix management client deadlock) posted (#1) for review on master by

Comment 2 Worker Ant 2017-12-06 21:10:12 UTC
REVIEW: https://review.gluster.org/18973 (glusterd: Allow volume stop to succeed if certain processes are already dead) posted (#2) for review on master by

Comment 3 Worker Ant 2017-12-07 16:16:19 UTC
COMMIT: https://review.gluster.org/18974 committed in master by  with a commit message- Fix management client deadlock

Ping notify is a NOOP for management daemons

Reviewers: sshreyas

Reviewed By: sshreyas

FB-commit-id: ec30b68

Change-Id: I8e121aaaa3ad268e5df057e03aa4b37a403c9ea0
BUG: 1522968
Signed-off-by: Kevin Vigor <kvigor>
Reviewed-on: https://review.gluster.org/16858
CentOS-regression: Gluster Build System <jenkins.org>
NetBSD-regression: NetBSD Build System <jenkins.org>
Smoke: Gluster Build System <jenkins.org>
Reviewed-by: Shreyas Siravara <sshreyas>

Comment 4 Worker Ant 2017-12-08 05:30:41 UTC
COMMIT: https://review.gluster.org/18973 committed in master by  with a commit message- glusterd: Allow volume stop to succeed if certain processes are already dead

Summary:
- Sometimes a the process that glusterd is trying to kill is already dead.
- In that case, if it can't find the pid, it should just continue on and not fail the entire operation.

Change-Id: Ic96952a8d31927446f648830ede6ccd82512663f
BUG: 1522968
Reviewed-on: https://review.gluster.org/18234
Smoke: Gluster Build System <jenkins.org>
Reviewed-by: Shreyas Siravara <sshreyas>
CentOS-regression: Gluster Build System <jenkins.org>
Signed-off-by: Ana M. Neri <amnerip>

Comment 5 Shyamsundar 2018-03-15 11:23:27 UTC
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-4.0.0, please open a new bug report.

glusterfs-4.0.0 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/2018-March/000092.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.