summaryrefslogtreecommitdiffstats
path: root/xlators/features/glupy/src
diff options
context:
space:
mode:
authorSanju Rakonde <srakonde@redhat.com>2018-06-02 16:36:22 +0530
committerAtin Mukherjee <amukherj@redhat.com>2018-06-06 12:19:33 +0000
commitfe71ee74fd327f61aedc858699a953a0fe2cd8d4 (patch)
treea8c5c8ed534a87678dfaff03af56d9737a0d80fc /xlators/features/glupy/src
parent07ede8d44372eb30cedd21acf87ab605229c39ea (diff)
glusterd: gluster v status is showing wrong status for glustershd
When we restart the bricks, connect and disconnect events happen for glustershd. glusterd use two threads to handle disconnect and connects events from glustershd. When we restart the bricks we'll get both disconnect and connect events. So both the threads will compete for the big lock. We want disconnect event to finish before connect event. But If connect thread gets the big lock first, it sets svc->online to true, and then disconnect thread will et svc->online to false. So, glustershd will be disconnected from glusterd and wrong status is shown. After killing shd, glusterd sleeps for 1 second. To avoid the problem, If glusterd releses the lock before sleep and acquires it after sleep, disconnect thread will get a chance to handle the glusterd_svc_common_rpc_notify before other thread completes connect event. Change-Id: Ie82e823fdfc936feb7c0ae10599297b050ee9986 fixes: bz#1585391 Signed-off-by: Sanju Rakonde <srakonde@redhat.com>
Diffstat (limited to 'xlators/features/glupy/src')
0 files changed, 0 insertions, 0 deletions