[Bugs] [Bug 1421719] volume stop generates error log

bugzilla at redhat.com bugzilla at redhat.com
Wed Feb 15 22:14:40 UTC 2017


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

Jeff Darcy <jdarcy at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jdarcy at redhat.com



--- Comment #2 from Jeff Darcy <jdarcy at redhat.com> ---
Is this really *constant*?  When I did this one one of my own machines, I got
exactly two of these messages - one per brick.  How many bricks was your test
using?

This is probably because the RPC connection was closed while the
GLUSTERD_BRICK_TERMINATE requests themselves were still outstanding (see
glusterfs_handle_terminate).  This isn't seen in the non-multiplexing case
because then we just send a SIGKILL instead of an RPC, but that's not an option
here.  Workarounds are likely to require significant rearranging of a control
flow that has already proven quite fragile, which will be more disruptive than
some log messages, so I would recommend against spending time on this until
true release blockers have been fixed.

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


More information about the Bugs mailing list