[Bugs] [Bug 1252680] probing and detaching a peer generated a CRITICAL error - "Could not find peer" in glusterd logs

[bugzilla at redhat.com]

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



--- Comment #2 from Anand Avati <aavati at redhat.com> ---
COMMIT: http://review.gluster.org/11886 committed in release-3.7 by Atin
Mukherjee (amukherj at redhat.com) 
------
commit a40f9b42390d1143c2bf6dc710414c11ceb6cc22
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Thu Apr 16 17:54:24 2015 +0530

    glusterd: log improvement in glusterd_peer_rpc_notify

    Backport of http://review.gluster.org/#/c/10272/

    If ping time out is enabled glusterd can receive a disconnect event from a
peer
    which has been already deleted resulting into a critical log printed. This
patch
    ensures that critical message is logged only when its a connect event.

    Change-Id: I67d9aa3f60195e08af7dfc8a42683422aaf90a00
    BUG: 1252680
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: http://review.gluster.org/10272
    Tested-by: Gluster Build System <jenkins at build.gluster.com>
    Reviewed-by: Gaurav Kumar Garg <ggarg at redhat.com>
    Tested-by: NetBSD Build System <jenkins at build.gluster.org>
    Reviewed-by: Krishnan Parthasarathi <kparthas at redhat.com>
    Reviewed-on: http://review.gluster.org/11886
    Reviewed-by: Anand Nekkunti <anekkunt at redhat.com>

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