|author||Ravishankar N <firstname.lastname@example.org>||2020-08-19 11:14:25 +0530|
|committer||Ravishankar N <email@example.com>||2020-08-20 07:35:04 +0000|
afr: add null check for thin-arbiter gfid.
Problem: Lookup/creation of thin-arbiter ID file happens in background during mounting. On new volumes, if the ID file creation is in progress, and a FOP fails on data brick, a post-op (xattrop) is attemtped on TA. Since the TA file's gfid is null at this point, the ASSERT checks in protocol/ client causes a crash. Fix: Given that we decided to do Lookup/creation of thin-arbiter in background, fail the other AFR FOPS on TA if the ID file's gfid is null instead of winding it down to protocol/client. Also remove afr_changelog_thin_arbiter_post_op() which seems to be dead code. Updates: #763 Change-Id: I70dc666faf55cc5c8f7cf8e7d36085e4fa399c4d Signed-off-by: Ravishankar N <firstname.lastname@example.org>
Diffstat (limited to 'tests/bugs/glusterd/bug-857330/xml.t')
0 files changed, 0 insertions, 0 deletions