Red Hat Bugzilla – Bug 1279362
Monitor should restart the worker process when Changelog agent dies
Last modified: 2016-04-19 03:47:50 EDT
+++ This bug was initially created as a clone of Bug #1277076 +++
Description of problem:
Geo-replication will not detect if Changelog agent dies. Status shows all good but without any progress since Changelog Agent is not available.
Version-Release number of selected component (if applicable):
Mainline and 3.7.x
Steps to Reproduce:
1. Start Geo-replication and Wait till Status becomes "Active"
2. Kill Agent process and check the Geo-replication status(ps aux | grep gsyncd | grep agent)
Status shows "Active" even though status is "Faulty"
Status should show "Faulty" and Monitor should respawn the worker
--- Additional comment from Vijay Bellur on 2015-11-02 04:34:34 EST ---
REVIEW: http://review.gluster.org/12485 (geo-rep: Kill Geo-rep Worker when Agent process dies) posted (#1) for review on master by Aravinda VK (firstname.lastname@example.org)
--- Additional comment from Vijay Bellur on 2015-11-02 06:49:57 EST ---
REVIEW: http://review.gluster.org/12485 (geo-rep: Kill Geo-rep Worker when Agent process dies) posted (#2) for review on master by Aravinda VK (email@example.com)
Patch sent Upstream for review
COMMIT: http://review.gluster.org/12550 committed in release-3.7 by Venky Shankar (firstname.lastname@example.org)
Author: Aravinda VK <email@example.com>
Date: Fri Oct 30 17:06:58 2015 +0530
geo-rep: Kill Geo-rep Worker when Agent process dies
When Changelog agent process dies, Geo-replication fails to detect
and worker will run without respective Changelog agent. Status shows
Active/Passive without any progress.
With this patch, Worker process gets killed whenever Changelog
Signed-off-by: Aravinda VK <firstname.lastname@example.org>
Tested-by: NetBSD Build System <email@example.com>
Tested-by: Gluster Build System <firstname.lastname@example.org>
Reviewed-by: Venky Shankar <email@example.com>
Reviewed-by: Kotresh HR <firstname.lastname@example.org>
(cherry picked from commit 5d1ff7efd6ab3bd29a29922a9ea1e1aaf02544ad)
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.7.7, please open a new bug report.
glusterfs-3.7.7 has been announced on the Gluster mailinglists , packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist  and the update infrastructure for your distribution.