REVIEW: http://review.gluster.org/8151 (geo-rep: minimize xsync crawl usage) posted (#2) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8151 (geo-rep: Set upper limit to xsync crawl) posted (#3) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8151 (geo-rep: minimize xsync crawl usage and set upper limit to xsync crawl) posted (#4) for review on master by Aravinda VK (avishwan)
*** Bug 1112520 has been marked as a duplicate of this bug. ***
REVIEW: http://review.gluster.org/8151 (geo-rep: minimize xsync crawl usage and set upper limit to xsync crawl) posted (#5) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8151 (geo-rep: minimize xsync crawl usage and set upper limit to xsync crawl) posted (#6) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8151 (geo-rep: minimize xsync crawl usage and set upper limit to xsync crawl) posted (#7) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8151 (geo-rep: minimize xsync crawl usage and set upper limit to xsync crawl) posted (#8) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8151 (geo-rep: minimize xsync crawl usage and set upper limit to xsync crawl) posted (#9) for review on master by Aravinda VK (avishwan)
REVIEW: http://review.gluster.org/8151 (geo-rep: minimize xsync crawl usage and set upper limit to xsync crawl) posted (#10) for review on master by Aravinda VK (avishwan)
COMMIT: http://review.gluster.org/8151 committed in master by Venky Shankar (vshankar) ------ commit f4110bed9230025ef7cac8e550057e316f9de1cb Author: Aravinda VK <avishwan> Date: Mon Jun 23 13:43:20 2014 +0530 geo-rep: minimize xsync crawl usage and set upper limit to xsync crawl For effective handling of deletes and renames use history crawl as much as possible. History crawl will run in loop till it syncs all data before live changelog time. When it uses xsync crawl(fallback when changelog not available, or very first crawl) it sets upper limit to crawl. After completing History crawl, it checks actual end time returned by history api to compare with register time, if actual end is less than register time then run history crawl one more time. If first turn history processing time is less than the CHANGELOG ROLLOVER TIME then sleep for the difference, After sleep if it is guaranteed that rollover will happen and switches to live changelog consumption without switching to xsync. This sleep is only when history processing completed < CHANGELOG_ROLLOVER_TIME and sleep only after the first turn, So will not affect the performance. BUG: 1112238 Change-Id: I644ef24b07e42e81cec96a025ebd21244a555ec0 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/8151 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Venky Shankar <vshankar> Tested-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.7.0, please open a new bug report. glusterfs-3.7.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://thread.gmane.org/gmane.comp.file-systems.gluster.devel/10939 [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user