summaryrefslogtreecommitdiffstats
path: root/libglusterfs/Makefile.am
diff options
context:
space:
mode:
authorVenky Shankar <vshankar@redhat.com>2013-08-07 16:10:25 +0530
committerAnand Avati <avati@redhat.com>2013-09-04 20:42:31 -0700
commit9ccdba413ff12956df2221fce91b220300479d23 (patch)
tree9b1ae49555f53c9cc9164661268f8ab3c1cb43e0 /libglusterfs/Makefile.am
parent07bb6118677119fd21ff38d51b4cefd06c0ad35a (diff)
gsyncd / geo-rep: introduce "recovery" mode
This mode introduces and optimized recovery of master, used during failover-failback cases. Files are only transferred if they are identified as changed on the slave. A normal failback mechanism would be just to reverse the direction of geo-replication syncing. Doing this is the correct way but could be time consuming. "Recovery" mode optimizes this by identifying files (as skipping them) duing the one-shot crawl. NOTE: Use this mode when you are _absolutely_ sure that the namespace on the master is intact, ie. there is number of files in master is equal to the number of files in the slave, but the slave was written to (after a failover) when master was brought back up. - gluster volume geo <MV> <SLAVE>::<SV> config special_sync_mode recover - gluster volume geo <MV> <SLAVE>::<SV> start Change-Id: Idb698949e4e86698b15d04a35d33095562f51714 BUG: 994462 Original Author: Venky Shankar <vshankar@redhat.com> Signed-off-by: Venky Shankar <vshankar@redhat.com> Reviewed-on: http://review.gluster.org/5515 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Avra Sengupta <asengupt@redhat.com> Tested-by: Avra Sengupta <asengupt@redhat.com> Reviewed-by: Anand Avati <avati@redhat.com>
Diffstat (limited to 'libglusterfs/Makefile.am')
0 files changed, 0 insertions, 0 deletions