Red Hat Bugzilla – Bug 1039008
Dist-geo-rep : After checkpoint set, status detail doesn't show updated checkpoint info until second execution.
Last modified: 2015-07-29 00:30:27 EDT
Description of problem: After checkpoint set, status detail doesn't show updated checkpoint info until second execution. Version-Release number of selected component (if applicable):glusterfs-3.4.0.46geo-1. How reproducible: happens everytime Steps to Reproduce: 1.create and start a geo-rep relationship between master and slave. 2.create some data on master. 2.set the checkpoint. 3.run geo-rep status, and run it second time. Actual results: It geo-rep status doesn't show the updated checkpoint info until second execution. Expected results: It should show the info in the first execution of the geo-rep status. Additional info:
Verified with the build:glusterfs-3.7.0-2.el6rhs.x86_64 Checkpoint information is available with the first attempt after checkpoint is set. [root@georep1 scripts]# gluster volume geo-replication master 10.70.46.154::slave config checkpoint now geo-replication config updated successfully [root@georep1 scripts]# gluster volume geo-replication master 10.70.46.154::slave config status detail Invalid option geo-replication command failed [root@georep1 scripts]# gluster volume geo-replication master 10.70.46.154::slave status detail MASTER NODE MASTER VOL MASTER BRICK SLAVE USER SLAVE SLAVE NODE STATUS CRAWL STATUS LAST_SYNCED ENTRY DATA META FAILURES CHECKPOINT TIME CHECKPOINT COMPLETED CHECKPOINT COMPLETION TIME --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- georep1 master /rhs/brick1/b1 root 10.70.46.154::slave 10.70.46.101 Active Changelog Crawl 2015-05-21 15:38:00 0 86 0 0 2015-05-21 15:39:52 No N/A georep1 master /rhs/brick2/b2 root 10.70.46.154::slave 10.70.46.101 Active Changelog Crawl 2015-05-21 15:38:00 0 79 0 0 2015-05-21 15:39:52 No N/A georep3 master /rhs/brick1/b1 root 10.70.46.154::slave 10.70.46.154 Passive N/A N/A N/A N/A N/A N/A N/A N/A N/A georep3 master /rhs/brick2/b2 root 10.70.46.154::slave 10.70.46.154 Passive N/A N/A N/A N/A N/A N/A N/A N/A N/A georep2 master /rhs/brick1/b1 root 10.70.46.154::slave 10.70.46.103 Passive N/A N/A N/A N/A N/A N/A N/A N/A N/A georep2 master /rhs/brick2/b2 root 10.70.46.154::slave 10.70.46.103 Passive N/A N/A N/A N/A N/A N/A N/A N/A N/A [root@georep1 scripts]# Moving the bug to verified state
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-1495.html