[Bugs] [Bug 1384363] Polling failure errors getting when volume is started&stopped with SSL enabled setup.

bugzilla at redhat.com bugzilla at redhat.com
Tue Jan 10 06:28:50 UTC 2017


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



--- Comment #3 from Worker Ant <bugzilla-bot at gluster.org> ---
COMMIT: http://review.gluster.org/15632 committed in release-3.9 by Raghavendra
G (rgowdapp at redhat.com) 
------
commit 0e6a8452446003e9510cfad1dbece5c0b7151fdc
Author: Mohit Agrawal <moagrawa at redhat.com>
Date:   Wed Oct 26 18:41:42 2016 +0530

    rpc/socket.c : Modify gf_log message in socket_poller code in case of error

    Problem:  In case of SSL after stopping the volume if client(mount point)
is
              still trying to write the data on socket then it will throw an
EIO
              error on that socket and given this log message is captured at
every
              attempt this would flood the log file.

    Solution: To reduce the frequency of stored log message use
GF_LOG_OCCASIONALLY
              instead of gf_log.

    > BUG: 1381115
    > Change-Id: I66151d153c2cbfb017b3ebc4c52162278c0f537c
    > Signed-off-by: Mohit Agrawal <moagrawa at redhat.com>
    > Reviewed-on: http://review.gluster.org/15605
    > 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: Atin Mukherjee <amukherj at redhat.com>
    > (cherry picked from commit 070145750006c87099f945b4990a4460d814c21f)

    Change-Id: I9536dcb2cbf3f8082dccf049cbfb21a034f5eac1
    BUG: 1384363
    Signed-off-by: Mohit Agrawal <moagrawa at redhat.com>
    Reviewed-on: http://review.gluster.org/15632
    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: Atin Mukherjee <amukherj at redhat.com>
    Reviewed-by: Raghavendra G <rgowdapp at redhat.com>

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list