Description of problem: Changelog agent process goes to zombie when worker process is killed/goes to faulty How reproducible: Happens everytime Steps to Reproduce: 1. Setup geo-rep session between master and slave 2. kill any worker process in master (ps -ef | grep gsync | grep feedback, to get workers pid) Actual results: changelog agent process is going zombie Expected results: changelog agent process should not goto faulty Additional info:
REVIEW: http://review.gluster.org/7956 (feature/geo-rep: Fix for changelog agent becoming zombie.) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/7956 (feature/geo-rep: Fix for changelog agent becoming zombie.) posted (#2) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/7956 (feature/geo-rep: Fix for changelog agent becoming zombie.) posted (#3) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/7956 committed in master by Venky Shankar (vshankar) ------ commit b6c8b1b47838228611e1a619890effe8b2dd2ad3 Author: Kotresh H R <khiremat> Date: Fri May 30 17:03:30 2014 +0530 feature/geo-rep: Fix for changelog agent becoming zombie. Monitor process spawns changelog agent and is not wait on it, hence becoming zombie. When worker is dies/killed, it respawns both worker and corresponding agent leaving the earlier changelog agent in zombie state. This patch addresses this issue by waiting on agent process in montor process. Change-Id: I571b7d6487133848edca67e7446f1caa70ae01c9 BUG: 1103643 Signed-off-by: Kotresh H R <khiremat> Reviewed-on: http://review.gluster.org/7956 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Aravinda VK <avishwan> Reviewed-by: Venky Shankar <vshankar> Tested-by: Venky Shankar <vshankar>
A beta release for GlusterFS 3.6.0 has been released. Please verify if the release solves this bug report for you. In case the glusterfs-3.6.0beta1 release does not have a resolution for this issue, leave a comment in this bug and move the status to ASSIGNED. If this release fixes the problem for you, leave a note and change the status to VERIFIED. Packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update (possibly an "updates-testing" repository) infrastructure for your distribution. [1] http://supercolony.gluster.org/pipermail/gluster-users/2014-September/018836.html [2] http://supercolony.gluster.org/pipermail/gluster-users/
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.6.1, please reopen this bug report. glusterfs-3.6.1 has been announced [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://supercolony.gluster.org/pipermail/gluster-users/2014-November/019410.html [2] http://supercolony.gluster.org/mailman/listinfo/gluster-users