glusterfs.git/xlators/mgmt/glusterd/src/glusterd-volgen.c, branch v3.3.0qa12

glusterd: cleanup of volinfo '*_count' definitions

2011-09-23T13:48:32+00:00

earlier, sub_count was having different meaning depending on the
volume type.

now, for replica and stripe count, one can directly access the
'replica_count' or 'stripe_count' to get the corresponding
value from the volume info. 'sub_count' is preserved as is for backward
compatibility. there is a new variable 'dist_leaf_count' to get
info about how many bricks are present in one distribute sub volume.

Change-Id: I5ea1c8f9ae08f584cca63b91ba69035c7e4350ca
BUG: 3158
Reviewed-on: http://review.gluster.com/435
Reviewed-by: Krishnan Parthasarathi 
Tested-by: Gluster Build System

glusterd-volgen: prevent a crash when volume type is stripe-replicate

2011-09-23T13:31:23+00:00

when volgen tries to check for decommissioned nodes, a check for
stripe replicate volume was missed

Change-Id: Ie3aa97da2ec0d94fcf65f96bb4006b3fb54f59dc
BUG: 3616
Reviewed-on: http://review.gluster.com/494
Tested-by: Gluster Build System 
Reviewed-by: Krishnan Parthasarathi

mgmt/glusterd: Create volfile in correct path

2011-09-21T08:14:49+00:00

Change-Id: Ie52e4b1a338282f2697e2ce374dd566d2c5cf5d1
BUG: 3586
Reviewed-on: http://review.gluster.com/475
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

Proactive self heal process implementation

2011-09-14T12:36:24+00:00

Change-Id: I96db0d94566ceabf1649f890318363f738c06553
BUG: 2458
Reviewed-on: http://review.gluster.com/403
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

support for de-commissioning a node using 'remove-brick'

2011-09-13T09:10:12+00:00

to achieve this, we now create volume-file with
'decommissioned-nodes' option in distribute volume, then just
perform the rebalance set of operations (with 'force' flag set).

now onwards, the 'remove-brick' (with 'start' option) operation tries
to migrate data from removed bricks to existing bricks.

'remove-brick' also supports similar options as of replace-brick.

* (no options) -> works as 'force', will have the current behavior
         of remove-brick, ie., no data-migration, volume changes.

* start  (starts remove-brick with data-migration/draining process,
          which takes care of migrating data and once complete, will
          commit the changes to volume file)
* pause  (stop data migration, but keep the volume file intact with
          extra options whatever is set)
* abort  (stop data-migration, and fall back to old configuration)
* commit (if volume is stopped, commits the changes to volumefile)
* force  (stops the data-migration and commits the changes to
          volume file)

Change-Id: I3952bcfbe604a0952e68b6accace7014d5e401d3
BUG: 1952
Reviewed-on: http://review.gluster.com/118
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

glusterd: free the allocated string to avoid memory leak

2011-09-12T09:31:37+00:00

Change-Id: I520abf3c57a15be8bb7dd1e92ad0b049ef5c8970
BUG: 3341
Reviewed-on: http://review.gluster.com/394
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

mgmt/glusterd: volume set help-xml format change

2011-09-12T04:47:55+00:00

Change-Id: I503364c855d52605e301f4d3c205af6c9fc0e1df
BUG: 3366
Reviewed-on: http://review.gluster.com/380
Tested-by: Gluster Build System 
Reviewed-by: Amar Tumballi

modify to the way we used XDR definitions files (.x files)

2011-09-07T17:48:52+00:00

Earlier:
step 1: copy the existing .x files to /tmp
step 2: generate '.[ch]' files using 'rpcgen .x'
step 3: check diff with the to the existing files, add only your part
        of changes back to the original file. (ignore other changes).
step 4: there is another file to write wrapper functions to convert
        structures to/from XDR buffers, update it with your new structure.
step 5: use these wrapper functions in the newly written procedures.
step 6: commit :-|

Now:
step 1: update (mostly adding only) the .x file
step 2: run '/extras/generate-xdr-files.sh .x' command
step 3: implement rpc procedure to handle the request/response.
step 4: commit :-)

Change-Id: I219f9159fc980438c86e847c6b030be96e595ea2
BUG: 3488
Reviewed-on: http://review.gluster.com/341
Tested-by: Gluster Build System 
Reviewed-by: Anand Avati

glusterd: Removed local cli lock

2011-09-05T06:58:46+00:00

This change contains,
- removal of the local cli lock used to serialize
cli ops to a glusterd.
- glusterd's state-machine can handle competing 'lockers' with
guaranteed progress.
- flush cluster lock on 'owner' disconnecting and as 'owner',
send unlock to all on first peer disconnect.

Change-Id: I25961436b0790b4196f2b3438b105c37279399ad
BUG: 3320
Reviewed-on: http://review.gluster.com/123
Tested-by: Gluster Build System 
Reviewed-by: Vijay Bellur

mgmt/glusterd: Initialize local variable in volgen

2011-08-22T09:50:26+00:00

Change-Id: I84b4f7c9c2787334ce67e5c3e0534953b691c8e0
BUG: 3460
Reviewed-on: http://review.gluster.com/295
Tested-by: Gluster Build System 
Reviewed-by: Raghavendra Bhat