[Bugs] [Bug 1434303] New: Move spit-brain msg in read txn to debug

[bugzilla at redhat.com]

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

            Bug ID: 1434303
           Summary: Move spit-brain msg in read txn to debug
           Product: GlusterFS
           Version: 3.10
         Component: replicate
          Keywords: Triaged
          Assignee: bugs at gluster.org
          Reporter: ravishankar at redhat.com
                CC: bugs at gluster.org
        Depends On: 1433838
            Blocks: 1434302



+++ This bug was initially created as a clone of Bug #1433838 +++

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.

--- Additional comment from Worker Ant on 2017-03-20 00:48:18 EDT ---

REVIEW: https://review.gluster.org/16879 (afr: do not mention split-brain in
log message in read_txn) posted (#3) for review on master by Ravishankar N
(ravishankar at redhat.com)

--- Additional comment from Worker Ant on 2017-03-20 05:39:30 EDT ---

REVIEW: https://review.gluster.org/16879 (afr: do not mention split-brain in
log message in read_txn) posted (#4) for review on master by Ravishankar N
(ravishankar at redhat.com)

--- Additional comment from Worker Ant on 2017-03-20 09:58:53 EDT ---

COMMIT: https://review.gluster.org/16879 committed in master by Pranith Kumar
Karampuri (pkarampu at redhat.com) 
------
commit 71e023fcaab0058f32fedc7b6b702040fdd85f46
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.

    Change-Id: Idb88b8ea362515279dc9b246f06b6b646c6d8013
    BUG: 1433838
    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>


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1433838
[Bug 1433838] Move spit-brain msg in read txn to debug
https://bugzilla.redhat.com/show_bug.cgi?id=1434302
[Bug 1434302] Move spit-brain msg in read txn to debug
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.