[Bugs] [Bug 1434303] Move spit-brain msg in read txn to debug
bugzilla at redhat.com
bugzilla at redhat.com
Mon Mar 27 13:57:16 UTC 2017
https://bugzilla.redhat.com/show_bug.cgi?id=1434303
--- Comment #2 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/16934 committed in release-3.10 by
Shyamsundar Ranganathan (srangana at redhat.com)
------
commit a25ea72ce662122318778c49a9366a9afd4902dc
Author: Ravishankar N <ravishankar at redhat.com>
Date: Sun Mar 19 22:42:33 2017 +0530
afr: do not mention split-brain in log message in read_txn
I am seeing a lot of messages in qe/customer logs where read_txn
complains that file is possibly in split-brain because of no readable
subvol being found, does inode refresh and then there is no split-brain
message post the inode refresh. This means that a lookup was not issued
on the indoe to populate 'readable' or it can mean one brick is source
for data and the other for metadata, making readable to be zero (because
readable=intersection of (data,metadata readable) since commit
7a1c1e290470149696.
Since we anyway log actual split-brains post inode-refresh, move this
message to DEBUG log level.
> Signed-off-by: Ravishankar N <ravishankar at redhat.com>
> Reviewed-on: https://review.gluster.org/16879
> Reviewed-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
> Tested-by: Pranith Kumar Karampuri <pkarampu at redhat.com>
> Smoke: Gluster Build System <jenkins at build.gluster.org>
> NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
> CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
(cherry picked from commit 71e023fcaab0058f32fedc7b6b702040fdd85f46)
Change-Id: Idb88b8ea362515279dc9b246f06b6b646c6d8013
BUG: 1434303
Reviewed-on: https://review.gluster.org/16934
Tested-by: Ravishankar N <ravishankar at redhat.com>
Smoke: Gluster Build System <jenkins at build.gluster.org>
NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
Reviewed-by: Pranith Kumar Karampuri <pkarampu 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=MPeBOHthq0&a=cc_unsubscribe
More information about the Bugs
mailing list