[Bugs] [Bug 1541438] quorum-reads option can give inconsistent reads

[bugzilla at redhat.com]

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



--- Comment #1 from Karthik U S <ksubrahm at redhat.com> ---
Description of problem:
For a file, Brick-A has pending operations on Brick-B, Brick-B has pending
operations on Brick-C and Brick-C has pending operations on Brick-A. Since no
two other bricks are blaming one brick any of these bricks can be considered as
a good copy and a heal can be done. Reads will fail until heal happens.
The consistent read issue we found happens when Any one of the bricks go down
in this state. If Brick-A goes down, Reads will be served from Brick-B and if
Brick-B goes down Reads will be served from Brick-C. If Brick-C goes down reads
will be served from Brick-A. All these reads could give different content.


Version-Release number of selected component (if applicable):


How reproducible:
It is extremely difficult to hit this case. We are mostly going to simulate it
by putting breakpoints in gdb.

-- 
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=XnS0GBsQ2A&a=cc_unsubscribe