REVIEW: http://review.gluster.org/7945 (feature/geo-rep: Fix skipped files logging.) posted (#1) for review on master by Kotresh HR (khiremat)
COMMIT: http://review.gluster.org/7945 committed in master by Venky Shankar (vshankar) ------ commit 1dc824c6180ba7d2a620c5a660bdc5cabe7aabc1 Author: Kotresh H R <khiremat> Date: Fri May 30 01:43:15 2014 +0530 feature/geo-rep: Fix skipped files logging. When changelog is failed to process even after max retries, files are skipped but were not logging. This patch addresses this issue to log the skipped files. Change-Id: Ic617e4151231fe18a171efa57a119e21164e1a6a BUG: 1103577 Signed-off-by: Kotresh H R <khiremat> Reviewed-on: http://review.gluster.org/7945 Reviewed-by: Aravinda VK <avishwan> Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Venky Shankar <vshankar> Tested-by: Venky Shankar <vshankar>
Here is the bug description for this: +++ This bug was initially created as a clone of Bug #1102594 +++ Description of problem: geo-rep doesn't log the list of skipped files after it failed to process the changelog. it logs logs like this, >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> [2014-05-29 14:29:22.645479] W [master(/bricks/brick2/b5):278:regjob] <top>: Rsync: .gfid/83f38ae8-bc22-4b09-b305-4f6f19595564 [errcode: 23] [2014-05-29 14:29:22.646881] W [master(/bricks/brick2/b5):918:process] _GMaster: changelogs CHANGELOG.1401353904 could not be processed - moving on... [2014-05-29 14:29:22.680587] W [master(/bricks/brick2/b5):922:process] _GMaster: SKIPPED GFID = [2014-05-29 14:29:24.467900] I [master(/bricks/brick1/b1):476:crawlwrap] _GMaster: 11 crawls, 4 turns >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> Version-Release number of selected component (if applicable): mainline How reproducible: Happens everytime. Steps to Reproduce: 1. create geo-rep relationship between master(6x2 with 4 nodes) and slave(6x2 with 4 nodes). 2. create data on master using the command "crefi -T 1 -n 100 --multi -b 10 -d 10 --random --min=1K --max=10K /mnt/master/" 3. In the above given release just executing above command would result in failure to sync few files. 4. Check log files for skipped gifd Actual results: Geo-rep doesn't log, skipped gfid list Expected results: It should log skipped gfid list.
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