[Bugs] [Bug 1597230] glustershd crashes when index heal is launched before graph is initialized.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1597230

Worker Ant <bugzilla-bot at gluster.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|POST                        |MODIFIED



--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/20436 committed in release-3.12 by "jiffin
tony Thottan" <jthottan at redhat.com> with a commit message- glusterfsd: Do not
process GLUSTERD_BRICK_XLATOR_OP if graph is not ready

Backport of: https://review.gluster.org/#/c/20435/

Problem:
If glustershd gets restarted by glusterd due to node reboot/volume start force/
or any thing that changes shd graph (add/remove brick), and index heal
is launched via CLI, there can be a chance that shd receives this IPC
before the graph is fully active. Thus when it accesses
glusterfsd_ctx->active, it crashes.

Fix:
Since glusterd does not really wait for the daemons it spawned to be
fully initialized and can send the request as soon as rpc initialization has
succeeded, we just handle it at shd. If glusterfs_graph_activate() is
not yet done in shd but glusterd sends GD_OP_HEAL_VOLUME to shd,
we fail the request.

Change-Id: If6cc07bc5455c4ba03458a36c28b63664496b17d
BUG: 1597230
fixes: bz#1597230
Signed-off-by: Ravishankar N <ravishankar at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=bUAsZrVHei&a=cc_unsubscribe