[Bugs] [Bug 1460225] Not cleaning up stale socket file is resulting in spamming glusterd logs with warnings of "got disconnect from stale rpc"

[bugzilla at redhat.com]

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



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: https://review.gluster.org/17499 committed in master by Jeff Darcy
(jeff at pl.atyp.us) 
------
commit 801697cc08928660a8087d08122a3aed622f6790
Author: Atin Mukherjee <amukherj at redhat.com>
Date:   Fri Jun 9 17:10:00 2017 +0530

    glusterd: log stale rpc disconnects occasionally

    There might be situations where if a brick process is killed through
    SIGKILL (not SIGTERM) when brick mux is enabled glusterd will continue to
    receive disconnect events from the stale rpc which might flood the
    glusterd log. Fix is to use GF_LOG_OCCASIONALLY.

    Change-Id: I95a10c8be2346614e0a3458f98d9f99aab34800a
    BUG: 1460225
    Signed-off-by: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-on: https://review.gluster.org/17499
    Smoke: Gluster Build System <jenkins at build.gluster.org>
    NetBSD-regression: NetBSD Build System <jenkins at build.gluster.org>
    CentOS-regression: Gluster Build System <jenkins at build.gluster.org>
    Reviewed-by: Jeff Darcy <jeff at pl.atyp.us>

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