{"push_id":1624880288,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"71e023fcaab0058f32fedc7b6b702040fdd85f46","before":"e2a652ca6ba56235e6d64bf7df110afdc5f6ca27","commits":[{"sha":"71e023fcaab0058f32fedc7b6b702040fdd85f46","author":{"name":"Ravishankar N","email":"67f30892449d3a69e945b46c702f1af1231877a0@redhat.com"},"message":"afr: do not mention split-brain in log message in read_txn\n\nI am seeing a lot of messages in qe/customer logs where read_txn\ncomplains that file is possibly in split-brain because of no readable\nsubvol being found, does inode refresh and then there is no split-brain\nmessage post the inode refresh. This means that a lookup was not issued\non the indoe to populate 'readable' or it can mean one brick is source\nfor data and the other for metadata, making readable to be zero (because\nreadable=intersection of (data,metadata readable) since commit\n7a1c1e290470149696.\n\nSince we anyway log actual split-brains post inode-refresh, move this\nmessage to DEBUG log level.\n\nChange-Id: Idb88b8ea362515279dc9b246f06b6b646c6d8013\nBUG: 1433838\nSigned-off-by: Ravishankar N <ravishankar@redhat.com>\nReviewed-on: https://review.gluster.org/16879\nReviewed-by: Pranith Kumar Karampuri <pkarampu@redhat.com>\nTested-by: Pranith Kumar Karampuri <pkarampu@redhat.com>\nSmoke: Gluster Build System <jenkins@build.gluster.org>\nNetBSD-regression: NetBSD Build System <jenkins@build.gluster.org>\nCentOS-regression: Gluster Build System <jenkins@build.gluster.org>","distinct":true,"url":"https://api.github.com/repos/gluster/glusterfs/commits/71e023fcaab0058f32fedc7b6b702040fdd85f46"}]}
{"actor":{"display_login":"mscherer"}}