diff options
| author | Amar Tumballi <amar@gluster.com> | 2011-10-02 13:20:25 +0530 |
|---|---|---|
| committer | Vijay Bellur <vijay@gluster.com> | 2011-10-11 03:37:51 -0700 |
| commit | 513cd0d12e3b72e9a3714deeee251414e651213f (patch) | |
| tree | 9c8bfd6b8b53922d44d824610c904ab1523d6452 /xlators/mgmt/glusterd/src/glusterd-op-sm.h | |
| parent | 18071a240bd4c0d92f583632a7cdef1cd32bbe62 (diff) | |
glusterd: take off 'auto-commit' behavior of decommissioning
currently if 'remove-brick <BRICKS> start' is given, after all
the data is migrated, in the _cbk() function from rebalance
complete we used to re-write the volume file without the bricks.
But the flaw of this method is that, currently the _cbk() function
is called on only the node on which rebalance actually happens,
hence other nodes are not aware of this behavior. So, had to remove
the 'auto-commit', instead we want the user to issue a command
'remove-brick <Bricks> commit' (or 'force') explicitely to remove
the bricks
Change-Id: Ifdac1292095029429da502aa6e4c0cf4ee124990
BUG: 1952
Reviewed-on: http://review.gluster.com/551
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Shishir Gowda <shishirng@gluster.com>
Reviewed-by: Vijay Bellur <vijay@gluster.com>
Diffstat (limited to 'xlators/mgmt/glusterd/src/glusterd-op-sm.h')
0 files changed, 0 insertions, 0 deletions