Bug 1384363
| Summary: | Polling failure errors getting when volume is started&stopped with SSL enabled setup. | ||
|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Mohit Agrawal <moagrawa> |
| Component: | glusterd | Assignee: | bugs <bugs> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.9 | CC: | amukherj, bsrirama, bugs, rcyriac, rhinduja, rhs-bugs, storage-qa-internal, vbellur |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | glusterfs-3.9.1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | 1336377 | Environment: | |
| Last Closed: | 2017-03-08 10:23:55 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1336377, 1349709, 1359651, 1359654, 1384356 | ||
|
Description
Mohit Agrawal
2016-10-13 07:51:33 UTC
REVIEW: http://review.gluster.org/15632 (rpc/socket.c : Modify gf_log message in socket_poller code in case of error) posted (#1) for review on release-3.9 by MOHIT AGRAWAL (moagrawa) REVIEW: http://review.gluster.org/15632 (rpc/socket.c : Modify gf_log message in socket_poller code in case of error) posted (#2) for review on release-3.9 by MOHIT AGRAWAL (moagrawa) COMMIT: http://review.gluster.org/15632 committed in release-3.9 by Raghavendra G (rgowdapp) ------ commit 0e6a8452446003e9510cfad1dbece5c0b7151fdc Author: Mohit Agrawal <moagrawa> 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> > Reviewed-on: http://review.gluster.org/15605 > Smoke: Gluster Build System <jenkins.org> > NetBSD-regression: NetBSD Build System <jenkins.org> > CentOS-regression: Gluster Build System <jenkins.org> > Reviewed-by: Atin Mukherjee <amukherj> > (cherry picked from commit 070145750006c87099f945b4990a4460d814c21f) Change-Id: I9536dcb2cbf3f8082dccf049cbfb21a034f5eac1 BUG: 1384363 Signed-off-by: Mohit Agrawal <moagrawa> Reviewed-on: http://review.gluster.org/15632 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Raghavendra G <rgowdapp> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.9.1, please open a new bug report. glusterfs-3.9.1 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] http://lists.gluster.org/pipermail/gluster-users/2017-January/029725.html [2] https://www.gluster.org/pipermail/gluster-users/ |