diff options
| author | Mohit Agrawal <moagrawal@redhat.com> | 2020-06-09 15:38:12 +0530 |
|---|---|---|
| committer | gluster-ant <bugzilla-bot@gluster.org> | 2020-06-09 15:38:12 +0530 |
| commit | 372881377ccef2dd34412ae9c70f3d3ab1aa60c5 (patch) | |
| tree | 38f3630d6b65b1803bf301244c168d25a539f8cb /cli/src/cli-xml-output.c | |
| parent | 24781bf6a57f4d15fb09c1744f2f0813444bc881 (diff) | |
| download | glusterfs-372881377ccef2dd34412ae9c70f3d3ab1aa60c5.tar.gz glusterfs-372881377ccef2dd34412ae9c70f3d3ab1aa60c5.tar.xz glusterfs-372881377ccef2dd34412ae9c70f3d3ab1aa60c5.zip | |
test: Test case brick-mux-validation-in-cluster.t is failing on RHEL-8
Brick process are not properly attached on any cluster node while
some volume options are changed on peer node and glusterd is down on
that specific node.
Solution: At the time of restart glusterd it got a friend update request
from a peer node if peer node having some changes on volume.If the brick
process is started before received a friend update request in that case
brick_mux behavior is not workingproperly. All bricks are attached to
the same process even volumes options are not the same. To avoid the
issue introduce an atomic flag volpeerupdate and update the value while
glusterd has received a friend update request from peer for a specific
volume.If volpeerupdate flag is 1 volume is started by
glusterd_import_friend_volume synctask
Change-Id: I4c026f1e7807ded249153670e6967a2be8d22cb7
Credit: Sanju Rakaonde <srakonde@redhat.com>
fixes: #1290
Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>
Diffstat (limited to 'cli/src/cli-xml-output.c')
0 files changed, 0 insertions, 0 deletions