Description of problem: Add new feature to schedule Geo-replication when required. Instead of running always, schedule to run once a day or twice a day.
REVIEW: http://review.gluster.org/13279 (geo-rep: Script to Schedule Geo-replication) posted (#1) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/13279 (geo-rep: Script to Schedule Geo-replication) posted (#2) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/13279 (geo-rep: Script to Schedule Geo-replication) posted (#3) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/13279 committed in master by Venky Shankar (vshankar) ------ commit d7e052ee24b3e09f2e76c2fdb980e33e74d2a855 Author: Aravinda VK <avishwan> Date: Fri Jan 22 12:11:18 2016 +0530 geo-rep: Script to Schedule Geo-replication This script can be used to run Geo-replication when required. can be scheduled using cron job to run Geo-replication. This script does the following, 1. Stop Geo-replication if Started 2. Start Geo-replication 3. Set Checkpoint 4. Check the Status and see Checkpoint is Complete.(LOOP) 5. If checkpoint complete, Stop Geo-replication Usage: python /usr/share/glusterfs/scripts/schedule_georep.py <MASTERVOL> \ <SLAVEHOST> <SLAVEVOL> For example, python /usr/share/glusterfs/scripts/schedule_georep.py gv1 fvm1 gv2 To schedule the Geo-replication to run once in a day using cron, # Run daily at 08:30pm 30 20 * * * root python /usr/share/glusterfs/scripts/schedule_georep.py \ --no-color gv1 fvm1 gv2 >> /var/log/glusterfs/schedule_georep.log 2>&1 BUG: 1300956 Change-Id: I6b1e2ddbf7fc09ef621499b57ae230fd4dbbd9a6 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/13279 Smoke: Gluster Build System <jenkins.com> Reviewed-by: Kotresh HR <khiremat> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> Reviewed-by: Venky Shankar <vshankar>
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