Bug 1210965
Summary: | Geo-replication very slow, not able to sync all the files to slave | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | Aravinda VK <avishwan> | |
Component: | geo-replication | Assignee: | Aravinda VK <avishwan> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | urgent | Docs Contact: | ||
Priority: | urgent | |||
Version: | mainline | CC: | aavati, bkunal, bugs, csaba, gluster-bugs, nlevinki, rhs-bugs, sasundar, storage-qa-internal | |
Target Milestone: | --- | Keywords: | Reopened | |
Target Release: | --- | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.8rc2 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | 1210719 | |||
: | 1217930 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-16 12:49:31 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1210719 | |||
Bug Blocks: | 1217930 |
Description
Aravinda VK
2015-04-11 14:45:16 UTC
REVIEW: http://review.gluster.org/10202 (geo-rep: Limit number of changelogs to process in batch) posted (#1) for review on master by Aravinda VK (avishwan) REVIEW: http://review.gluster.org/10202 (geo-rep: Limit number of changelogs to process in batch) posted (#2) for review on master by Aravinda VK (avishwan) COMMIT: http://review.gluster.org/10202 committed in master by Vijay Bellur (vbellur) ------ commit 428933dce2c87ea62b4f58af7d260064fade6a8b Author: Aravinda VK <avishwan> Date: Sat Apr 11 20:03:47 2015 +0530 geo-rep: Limit number of changelogs to process in batch Changelog processing is done in batch, for example if 10 changelogs available for processing then process all at once. Collect Entry, Meta and Data operations separately, All the entry operations like CREATE, MKDIR, MKNOD, LINK, UNLINK will be executed first then rsync will be triggered for whole batch. Stime will get updated once the complete batch is complete. In case of large number of Changelogs in a batch, If geo-rep fails after Entry operations, but before rsync then on restart, it again starts from the beginning since stime is not updated. It has to process all the changelogs again. While processing same changelogs again, all CREATE will get EEXIST since all the files created in previous run. Big hit for performance. With this patch, Geo-rep limits number of changelogs per batch based on Changelog file size. So that when geo-rep fails it has to retry only last batch changelogs since stime gets updated after each batch. BUG: 1210965 Change-Id: I844448c4cdcce38a3a2e2cca7c9a50db8f5a9062 Signed-off-by: Aravinda VK <avishwan> Reviewed-on: http://review.gluster.org/10202 Reviewed-by: Kotresh HR <khiremat> Tested-by: NetBSD Build System Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur> 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. 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 |