summaryrefslogtreecommitdiffstats
path: root/xlators/performance/write-behind/src/write-behind.c
diff options
context:
space:
mode:
authorKrishnan Parthasarathi <kp@gluster.com>2012-02-13 19:15:17 +0530
committerVijay Bellur <vijay@gluster.com>2012-03-27 10:34:13 -0700
commitc3c4ee24a64a2447f77788cb84559f1e07a21e04 (patch)
tree876b9712f91b6ee84d61d2a971756d0649524d03 /xlators/performance/write-behind/src/write-behind.c
parent3184ad0f88255fdec5a33b29790f677848c422e3 (diff)
glusterd: Fixed replace-brick commit_force algo.
- commit force subcommand of replace-brick (rb) should be allowed even if source brick is (irrecoverably) offline. - modified rb_timer to be active only for start subcommand. This is important since, the rb timer event relies on src_brick and dst_brick objects to be 'alive' when it 'happens'. In the case of abort/commit/commit force it is very likely that src_brick and/or dst_brick objects could have been destroyed. Change-Id: Ib8b8a4d690fbdd6f99b8aff306490eb59c54a437 BUG: 772845 Signed-off-by: Krishnan Parthasarathi <kp@gluster.com> Reviewed-on: http://review.gluster.com/2620 Tested-by: Gluster Build System <jenkins@build.gluster.com> Reviewed-by: Amar Tumballi <amarts@redhat.com> Reviewed-by: Vijay Bellur <vijay@gluster.com>
Diffstat (limited to 'xlators/performance/write-behind/src/write-behind.c')
0 files changed, 0 insertions, 0 deletions