+++ This bug was initially created as a clone of Bug #1101407 +++ Description of problem: geo-rep pause won't retain state after the reboot or restart of the worker process. Version-Release number of selected component (if applicable): glusterfs-api-3.6.0.7-1 How reproducible: Happens always. Steps to Reproduce: 1. create and start a geo-rep relationship between master and slave. 2. pause the geo-rep. 3. Then reboot one of the node Actual results: gsyncd won't retain state after the reboot. Expected results: gsyncd should retain state after the reboot. Additional info:
REVIEW: http://review.gluster.org/7885 (feature/geo-rep: Fix to retain pause state of gsyncd on restart.) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/7885 (feature/geo-rep: Fix to retain pause state of gsyncd on restart.) posted (#2) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/7885 (feature/geo-rep: Fix to retain pause state of gsyncd on restart.) posted (#3) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/7885 committed in master by Venky Shankar (vshankar) ------ commit 77498fdbbca8554880eae4b8f559b9d6876e35b7 Author: Kotresh H R <khiremat> Date: Sun May 25 23:41:48 2014 +0530 feature/geo-rep: Fix to retain pause state of gsyncd on restart. A new gsyncd options '--pause-on-start' is introduced. When node reboots, if the status is paused, gsyncd is started with this option. After gsyncd spawns worker and agent, worker will send SIGSTOP to negative pid of monitor to enter pause mode. Change-Id: I5aad82c9a9fc8c243f384940b77d25e26e520d6d BUG: 1101410 Signed-off-by: Kotresh H R <khiremat> Reviewed-on: http://review.gluster.org/7885 Reviewed-by: Aravinda VK <avishwan> Reviewed-by: Venky Shankar <vshankar> Tested-by: Venky Shankar <vshankar>
Works with hard reboot, but failed on soft reboot.
REVIEW: http://review.gluster.org/8097 (feature/geo-rep: Fix to retain pause state of gsyncd on restart.) posted (#1) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/8097 (feature/geo-rep: Fix to retain pause state of gsyncd on restart.) posted (#2) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/8097 (feature/geo-rep: Fix to retain pause state of gsyncd on restart.) posted (#3) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/8097 (feature/geo-rep: Fix to retain pause state of gsyncd on restart.) posted (#4) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/8097 (feature/geo-rep: Fix to retain pause state of gsyncd on restart.) posted (#5) for review on master by Kotresh HR (khiremat)
REVIEW: http://review.gluster.org/8097 (feature/geo-rep: Fix to retain pause state of gsyncd on restart) posted (#6) for review on master by Venky Shankar (vshankar)
COMMIT: http://review.gluster.org/8097 committed in master by Venky Shankar (vshankar) ------ commit 124ba991069099258e4e69ccf3eefae1c88ebb8c Author: Kotresh H R <khiremat> Date: Wed Jun 18 13:30:26 2014 +0530 feature/geo-rep: Fix to retain pause state of gsyncd on restart On soft reboot, geo-rep monitor is writing 'faulty' into status file. It should not do it if previous state is paused as glusterd depend on the state file on node restart. Change-Id: Idd45abf13350b087371935f1b4f6e1a346433d27 BUG: 1101410 Signed-off-by: Kotresh H R <khiremat> Reviewed-on: http://review.gluster.org/8097 Tested-by: Gluster Build System <jenkins.com> 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