+++ This bug was initially created as a clone of Bug #1393678 +++ Description of problem: If log-rsync-performance config is set using following command, workers restarts and causes reprocessing Changelogs which are processed before the config change. gluster volume geo-replication <MASTER> <SLAVEHOST>::<SLAVEVOL> config log-rsync-performance true --- Additional comment from Worker Ant on 2016-11-10 02:12:36 EST --- REVIEW: http://review.gluster.org/15816 (geo-rep: Do not restart workers when log-rsync-performance config change) posted (#1) for review on master by Aravinda VK (avishwan) --- Additional comment from Worker Ant on 2016-11-17 01:33:20 EST --- REVIEW: http://review.gluster.org/15816 (geo-rep: Do not restart workers when log-rsync-performance config change) posted (#2) for review on master by Aravinda VK (avishwan) --- Additional comment from Worker Ant on 2016-12-02 03:36:56 EST --- REVIEW: http://review.gluster.org/15816 (geo-rep: Do not restart workers when log-rsync-performance config change) posted (#3) for review on master by Aravinda VK (avishwan) --- Additional comment from Worker Ant on 2016-12-08 01:05:39 EST --- COMMIT: http://review.gluster.org/15816 committed in master by Aravinda VK (avishwan) ------ commit a268e2865c21ec8d2b4fed26715e986cfcc66fad Author: Aravinda VK <avishwan> Date: Thu Nov 10 12:35:30 2016 +0530 geo-rep: Do not restart workers when log-rsync-performance config change Geo-rep restarts workers when any of the configurations changed. We don't need to restart workers if tunables like log-rsync-performance is modified. With this patch, Geo-rep workers will get new "log-rsync-performance" config automatically without restart. BUG: 1393678 Change-Id: I40ec253892ea7e70c727fa5d3c540a11e891897b Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/15816 NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Smoke: Gluster Build System <jenkins.org> Reviewed-by: Kotresh HR <khiremat>
REVIEW: http://review.gluster.org/16069 (geo-rep: Do not restart workers when log-rsync-performance config change) posted (#1) for review on release-3.8 by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/16069 committed in release-3.8 by Aravinda VK (avishwan) ------ commit 8e468911139c561288dbfefe2bfdcac8c8cc0daa Author: Aravinda VK <avishwan> Date: Thu Nov 10 12:35:30 2016 +0530 geo-rep: Do not restart workers when log-rsync-performance config change Geo-rep restarts workers when any of the configurations changed. We don't need to restart workers if tunables like log-rsync-performance is modified. With this patch, Geo-rep workers will get new "log-rsync-performance" config automatically without restart. > Reviewed-on: http://review.gluster.org/15816 > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> > Smoke: Gluster Build System <jenkins.org> > Reviewed-by: Kotresh HR <khiremat> BUG: 1402728 Change-Id: I40ec253892ea7e70c727fa5d3c540a11e891897b Signed-off-by: Aravinda VK <avishwan> (cherry picked from commit a268e2865c21ec8d2b4fed26715e986cfcc66fad) Reviewed-on: http://review.gluster.org/16069 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Kotresh HR <khiremat>
REVIEW: http://review.gluster.org/16340 (geo-rep: Fix log-rsync-performance config issue) posted (#1) for review on release-3.8 by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/16340 committed in release-3.8 by Niels de Vos (ndevos) ------ commit 84a3d13d723fcfc7a6c194d9f34e031b20554984 Author: Aravinda VK <avishwan> Date: Mon Dec 12 13:06:15 2016 +0530 geo-rep: Fix log-rsync-performance config issue If log-rsync-performance config is not set, gconf.get_realtime will return None, Added default value as False if config file doesn't have this option set. > BUG: 1393678 > Change-Id: I89016ab480a16179db59913d635d8553beb7e14f > Signed-off-by: Aravinda VK <avishwan> > Reviewed-on: http://review.gluster.org/16102 > Smoke: Gluster Build System <jenkins.org> > Tested-by: Kotresh HR <khiremat> > Reviewed-by: Kotresh HR <khiremat> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> BUG: 1402728 Change-Id: I89016ab480a16179db59913d635d8553beb7e14f Signed-off-by: Kotresh HR <khiremat> Reviewed-on: http://review.gluster.org/16340 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Niels de Vos <ndevos>
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.8, please open a new bug report. glusterfs-3.8.8 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] https://lists.gluster.org/pipermail/announce/2017-January/000064.html [2] https://www.gluster.org/pipermail/gluster-users/