diff options
| author | yinkui <13965432176@163.com> | 2019-06-28 13:57:30 +0800 |
|---|---|---|
| committer | Amar Tumballi <amar@kadalu.io> | 2020-06-09 01:40:01 +0000 |
| commit | 06fa9869070146e8c832cb930536c66c91494fd8 (patch) | |
| tree | 059f99b90c8ecde4cff2e34dad8e6e6bdab2a00c /tests/bugs/glusterd/brick-mux-validation-in-cluster.t | |
| parent | d21d656bc4a91bf0e7b0d05df26a2bb8b3204891 (diff) | |
| download | glusterfs-06fa9869070146e8c832cb930536c66c91494fd8.tar.gz glusterfs-06fa9869070146e8c832cb930536c66c91494fd8.tar.xz glusterfs-06fa9869070146e8c832cb930536c66c91494fd8.zip | |
glusterd: To do full heal in different online node when do ec/afr full heal
For example:
We have 3 nodes and create ec 3*(2+1) volume for
test-disperse-0/test-disperse-1/test-disperse-2 when we do
'gluster v heal test full' in node-1 that can in node-1/
node-2/node-3 glustershd's get op=GF_EVENT_TRANSLATOR_OP
and then do full heal in different disperse group.
Let us say we have 2X(2+1) disperse with each brick
from different machine m0, m1, m2, m3, m4, m5. and candidate_max is m5.
and do full heal so '*index' is 3 and !gf_uuid_compare(MY_UUID, brickinfo->uuid)
will be true in m3,and then m3's glustershd will be the heal-xlator.
Id: I5c6762e6cfb375aed32d3fc11fe5eae3ee41aab4
Signed-off-by: yinkui <13965432176@163.com>
Change-Id: Ic7ef3ddfd30b5f4714ba99b4e7b708c927d68764
fixes: bz#1724948
Diffstat (limited to 'tests/bugs/glusterd/brick-mux-validation-in-cluster.t')
0 files changed, 0 insertions, 0 deletions