diff options
| author | Kaushal M <kaushal@redhat.com> | 2013-08-07 12:25:07 +0530 |
|---|---|---|
| committer | Vijay Bellur <vbellur@redhat.com> | 2013-08-18 07:24:02 -0700 |
| commit | e79be3d1655edb2b9f64a13e1fabae601c7d19e4 (patch) | |
| tree | 1e9a56e33b9b4135d55c20104db5c4e76590600c /xlators/mgmt/glusterd/src/glusterd-handler.c | |
| parent | c12fccc4732df63273e8d013fd471e1c8f3b7d22 (diff) | |
glusterd: Try to start all bricks on 'start force'
A volume would fail to start if any one of the bricks fails staging or
fails to start, even with the 'force' option. With this patch, when the
'force' option is given for a volume start, glusterd will continue and
start other bricks even if one fails staging or starting.
Also did a small fix in changelog, to prevent it crashing when it fails
to init.
Change-Id: I7efbd9ab13d12d69b0335ae54143fa17586f8f98
BUG: 994375
Signed-off-by: Kaushal M <kaushal@redhat.com>
Reviewed-on: http://review.gluster.org/5510
Reviewed-by: Venky Shankar <vshankar@redhat.com>
Reviewed-by: Amar Tumballi <amarts@redhat.com>
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Vijay Bellur <vbellur@redhat.com>
Diffstat (limited to 'xlators/mgmt/glusterd/src/glusterd-handler.c')
0 files changed, 0 insertions, 0 deletions