[Bugs] [Bug 1356942] Problem with persistant mount on quorum fail when using SSL

[bugzilla at redhat.com]

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

Atin Mukherjee <amukherj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
              Flags|                            |needinfo?(klas.mattsson at su.
                   |                            |se)



--- Comment #20 from Atin Mukherjee <amukherj at redhat.com> ---
(In reply to Klas Mattsson from comment #17)
> Mohit:
> That it goes read-only is expected, that is how it's supposed to work.
> That is the functionality I want (to prevent split-brain).
> 
> The problem is that with SSL, it doesn't recover even after quorum has been
> reached.
> 
> So, the following flow is expected:
> 1: A mount is working, 3 servers are functioning, quorum has been reached.
> 2: A mount is still working, 2 servers are functioning, quorum has been
> reached.
> 3: A mount has failed, 1 server is functioning, quorum has not been reached.
> 4: A mount starts working again, 2 servers are functioning, quorum been
> reached.
> 
> What actually happens:
> 1: A mount is working, 3 servers are functioning, quorum has been reached.
> 2: A mount is still working, 2 servers are functioning, quorum has been
> reached.
> 3: A mount has failed, 1 server is functioning, quorum has not been reached.
> 4: A mount is still failed, 2 servers are functioning, quorum been reached.

When you mention that quorum is reached, could you provide the output of
gluster peer status and gluster volume status?

> 5: A remount is required of the volume to make it work again, even though
> quorum has been reached.
> 
> For me, this does not happen when client.ssl and server.ssl is off, but
> happens when they are on.

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