glusterfs.git/xlators/features/marker/utils/syncdaemon/master.py, branch v3.4.4beta1

geo-rep / gsyncd,glusterd: do not hardcode socket path

2012-11-29T00:54:07+00:00

... in gsyncd python code. Indeed, use the configuration
mechanism to set it suitably from glusterd.

Change-Id: I9fe2088b14d28588d1e64fe892740cc5755b8365
BUG: 868877
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.org/4143
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

geo-rep / gsycnd: restore the generic signature for sendmark_regular

2012-07-30T18:18:20+00:00

Earlier fixes to 842330 changed the generic (*a, **kw) signature,
although that was not related to the issue.

We restore the generic signature as it was used for a reason
(proxy methods that do none or only algebraic transformations
on passed arguments idiomatically have generic signature, both
to serve as visual cue and agnosticism wrt. the inner API).

Change-Id: Ib609a3a58be53d78b7f1221a3c162c6aec8fd488
BUG: 842330
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.com/3754
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

gsyncd / geo-rep: Fix sendmark() invocation for Normal Mixin

2012-07-25T14:08:21+00:00

Change-Id: I0ae81ab01418becba83e401ec36c6db5323945e8
BUG: 842330
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.com/3725
Tested-by: Vijay Bellur 
Reviewed-by: Vijay Bellur

Fixes for gsyncd / geo-rep and FUSE listxattr

2012-07-24T09:45:05+00:00

This patch fixes two problems with recent changes to
Geo-Replication

First:
------
Recent changes to geo-replication relies on Rsync to tranfer
extended attributes. Essentially Rsync would invoke a listxattr()
and then getxattr() the set reutrned by listxattr() and finally
transfer it to the remote slave. Xattrs like security.selinux would
create problems as they are not allowed to be set explicitly (unless
there's a rule that allows this). So, to make Rsync behave sanely we
filter out all "*.selinux*" xattrs from listxattr() (which is getxattr()
with ->name as NULL).

Second:
-------
Python's "if {..} else {..}" shortcut ".. and .. or .." was misused here.
This is a straightforward fix by interchanging last two variables (classes
in this case). Also fix a typo in sendmark_regular() definition.

Change-Id: I097b5f5d88a36c7eef5560a78d4332948a545942
BUG: 842330
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.com/3714
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

gsyncd / geo-rep: Fix typo in 'purge' flow

2012-07-20T15:32:52+00:00

Change-Id: I6c329b895178545d16b0cb9f01ad116f5342f752
BUG: 841855
Signed-off-by: Venky Shankar 
Reviewed-on: http://review.gluster.com/3706
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

geo-rep / gsyncd: convert ignore-deletes to a mixin too

2012-07-19T17:16:12+00:00

Change-Id: I164a1d1dd5f15569afd6806834119a6844949df0
BUG: 841062
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.com/3684
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

geo-rep / gsyncd: add support for sending xtimes through rsync

2012-07-19T17:15:57+00:00

Note that in said mode metadata synchronization is best effort:
rsync syncs metadata at last so if rsync is interrupted in between
xattr sync and metadata sync stages, then file will be considered
in sync

Change-Id: I1c75eab33b0a1000abf3ad36b2d484a89eeda1bd
BUG: 841062
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.com/3683
Tested-by: Gluster Build System 
Reviewed-by: Venky Shankar

gsyncd / geo-rep : failover/failback

2012-06-13T15:39:06+00:00

This commit is based on Venky Shankar 's
original implementation. Let us first quote Venky's
description, then we summarize changes to his work.

------
First version of failover/failback.

Failback mechanism uses two exclusive modes:
  * blind-sync
    This mode works with xtime pairs (both master and slave) to
    identify candidated to sync the original master from the slave

  * wrapup-sync
    This mode is similar to the normal working of gsyncd except
    that orphaned entities in the gluster volume are not assigned
    xtimes. This prevents un-necessary transfer of data for such
    entities.

Modes can be enabled via:

  gluster volume geo-replication M S config special_sync_mode blind
  gluster volume geo-replication M S config special_sync_mode wrapup

To turn off the special modes (i.e. to revert to normal gsyncd behaviour) use:

  gluster volume geo-replication colon-d0 192.168.1.2::colon-d config \!special_sync_mode
------

Code has been refactored to meet following goals:

- make checkpointing work with special sync modes
- move out sync mode related conditionals from the crawl
  loop and make all decisions to be made at startup
  time
- be intrusive to the crawl loop to smallest possible degree
  (we will have to change/revisit it for other reasons,
  and the complexity of that should not increase)

So, xtime parsing/updating/evaluation that's specific to
the certain special modes are represented as mixin classes;
basic operation logic is in an abstract base class.
On startup, special-sync-mode tunable is dynamically dispatched
to the corresponding mixin and the actual master class is
derived from the chosen mixin and the ABS.

Change-Id: Ic9b8448f31ad4239a8200dc689f7d713662a67de
BUG: 830497
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.com/3541
Tested-by: Gluster Build System 
Reviewed-by: Venky Shankar

geo-rep: checkpointing

2012-06-13T15:37:41+00:00

- gluster vol geo-rep M S conf checkpoint 

  sets a checkpoint with LABEL (the keyword "now" is special,
  it's rendered to the label "as of ")
  that's used to refer to the checkpoint in the sequel.

  (Technically, gsyncd makes a note of the xtime of master's root
  as of setting the checkpoint, called the "checkpoint target".)

- gluster vol geo-rep M S conf \!checkpoint

  deletes the checkpoint.

- gluster vol geo-rep M S stat

  if status is OK, and there is a checkpoint configured, the checkpoint
  info is appended to status (either "not yet reached", or
  "completed at ").

  (Technically, the worker runs a thread that monitors / serializes /
  verifies checkpoint status, and answers checkpoint status requests
  through a UNIX socket; monitoring boils down to querying the xtime
  of slave's root and comparing with the target.)

- gluster vol geo-rep M S conf log-file | xargs grep checkpoint

  displays the checkpoint history. Set, delete and completion events
  are logged properly.

Change-Id: I4398e0819f1504e6e496b4209e91a0e156e1a0f8
BUG: 826512
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.com/3491
Tested-by: Gluster Build System 
Reviewed-by: Venky Shankar

geo-rep / gsyncd: typo fix

2012-05-19T12:27:41+00:00

fix topy.

Change-Id: I84df3e850dd24d9e86713dfa401c603a84a81ca6
BUG: 763302
Signed-off-by: Csaba Henk 
Reviewed-on: http://review.gluster.com/3375
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur