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 How reproducible: Always 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) Actual results: Status shows "Active" even though status is "Faulty" Expected results: Status should show "Faulty" and Monitor should respawn the worker
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 (avishwan)
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 (avishwan)
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