Bug 1251980
| Summary: | dist-geo-rep: geo-rep status shows Active/Passive even when all the gsync processes in a node are killed | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Saravanakumar <sarumuga> | |
| Component: | geo-replication | Assignee: | Saravanakumar <sarumuga> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | high | Docs Contact: | ||
| Priority: | high | |||
| Version: | mainline | CC: | avishwan, bkunal, bugs, chrisw, csaba, mzywusko, nlevinki, rcyriac, rhs-bugs, sarumuga, storage-qa-internal | |
| Target Milestone: | --- | Keywords: | ZStream | |
| Target Release: | --- | |||
| Hardware: | x86_64 | |||
| OS: | Linux | |||
| Whiteboard: | status | |||
| Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1249975 | |||
| : | 1276060 (view as bug list) | Environment: | ||
| Last Closed: | 2016-06-16 13:30:14 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: | 1033184, 1249973, 1249975 | |||
| Bug Blocks: | 1276060 | |||
|
Comment 1
Anand Avati
2015-08-10 13:19:30 UTC
REVIEW: http://review.gluster.org/11873 (geo-rep: Update geo-rep status, if monitor process is killed) posted (#2) for review on master by Saravanakumar Arumugam (sarumuga) REVIEW: http://review.gluster.org/11873 (geo-rep: Update geo-rep status, if monitor process is killed) posted (#3) for review on master by Saravanakumar Arumugam (sarumuga) REVIEW: http://review.gluster.org/11873 (geo-rep: Update geo-rep status, if monitor process is killed) posted (#4) for review on master by Saravanakumar Arumugam (sarumuga) REVIEW: http://review.gluster.org/11873 (geo-rep: Update geo-rep status, if monitor process is killed) posted (#5) for review on master by Saravanakumar Arumugam (sarumuga) REVIEW: http://review.gluster.org/11873 (geo-rep: Update geo-rep status, if monitor process is killed) posted (#6) for review on master by Saravanakumar Arumugam (sarumuga) COMMIT: http://review.gluster.org/11873 committed in master by Jeff Darcy (jdarcy) ------ commit 4d4c7d5dc54850dcf916083b2b1398d9bfe2bfe6 Author: Saravanakumar Arumugam <sarumuga> Date: Mon Aug 10 18:42:05 2015 +0530 geo-rep: Update geo-rep status, if monitor process is killed Problem: When the monitor process itself is getting killed, geo-rep session still shows as active. Status command will just pick up the content from the status file to show the output. Monitor process is the one which updates the Status file. When the monitor process itself gets killed, there is no way to update the status file. So, geo-rep session status command ends up showing last updated Status present in the status file. Solution: While getting the status output, check whether monitor process is running. If it is NOT running, update the status as STOPPED. Change-Id: I86a7ac1746dd8f27eef93658e992ef16f6068d9d BUG: 1251980 Signed-off-by: Saravanakumar Arumugam <sarumuga> Reviewed-on: http://review.gluster.org/11873 Tested-by: NetBSD Build System <jenkins.org> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Milind Changire <mchangir> Reviewed-by: Kotresh HR <khiremat> Reviewed-by: Jeff Darcy <jdarcy> 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.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |