diff options
| author | Ashish Pandey <aspandey@redhat.com> | 2018-12-21 14:31:15 +0530 |
|---|---|---|
| committer | Shyamsundar Ranganathan <srangana@redhat.com> | 2019-02-18 14:39:55 +0000 |
| commit | b2f561c069d38f5075907b9f5a255f585a602c79 (patch) | |
| tree | 0aa90b7120673e2f701d798c2f288d168fe38909 /tests/basic/fops-sanity.c | |
| parent | 183cac3a642ae4a1b750bc11673045fc0ff66a6d (diff) | |
cluster/thin-arbiter: Consider thin-arbiter before marking new entry changelog
If a fop to create an entry fails on one of the data brick,
we mark the pending changelog on the entry on brick for which
it was successful. This is done as part of post op phase to
make sure that entry gets healed even if it gets renamed to
some other path where its parent was not marked as bad.
As it happens as part of post op, we should consider thin-arbiter
to check if the brick, which was successful, is the good brick or not.
This will avoide split brain and other issues.
>Change-Id: I12686675be98f02f70a5186b3ed748c541514d53
>Signed-off-by: Ashish Pandey <aspandey@redhat.com>
Change-Id: I12686675be98f02f70a5186b3ed748c541514d53
updates: bz#1672314
Signed-off-by: Ashish Pandey <aspandey@redhat.com>
Diffstat (limited to 'tests/basic/fops-sanity.c')
0 files changed, 0 insertions, 0 deletions