Bug 1456405
| Summary: | Brick Multiplexing:dmesg shows request_sock_TCP: Possible SYN flooding on port 49152 and memory related backtraces | |||
|---|---|---|---|---|
| Product: | [Community] GlusterFS | Reporter: | Mohammed Rafi KC <rkavunga> | |
| Component: | protocol | Assignee: | bugs <bugs> | |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
| Severity: | urgent | Docs Contact: | ||
| Priority: | unspecified | |||
| Version: | mainline | CC: | amukherj, bugs, nchilaka, pkarampu, rhinduja, rhs-bugs, storage-qa-internal | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | brick-multiplexing | |||
| Fixed In Version: | glusterfs-3.12.0 | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | 1453145 | |||
| : | 1463517 (view as bug list) | Environment: | ||
| Last Closed: | 2017-09-05 17:32:34 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: | 1453145 | |||
| Bug Blocks: | 1463517 | |||
|
Comment 1
Mohammed Rafi KC
2017-05-29 10:41:07 UTC
REVIEW: https://review.gluster.org/17411 (protocol/server: make listen backlog value as configurable) posted (#1) for review on master by mohammed rafi kc (rkavunga) REVIEW: https://review.gluster.org/17412 (socket/reconfigure: reconfigure should be done on new dict) posted (#1) for review on master by mohammed rafi kc (rkavunga) COMMIT: https://review.gluster.org/17412 committed in master by Raghavendra G (rgowdapp) ------ commit 2168729011a0e835a8bdbde9cae7aaddd78a414d Author: Mohammed Rafi KC <rkavunga> Date: Mon May 29 16:19:40 2017 +0530 socket/reconfigure: reconfigure should be done on new dict In socket reconfigure, reconfigurations are doing with old dict values. It should be with new reconfigured dict values Change-Id: Iac5ad4382fe630806af14c99bb7950a288756a87 BUG: 1456405 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: https://review.gluster.org/17412 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp> REVIEW: https://review.gluster.org/17411 (protocol/server: make listen backlog value as configurable) posted (#2) for review on master by mohammed rafi kc (rkavunga) REVIEW: https://review.gluster.org/17411 (protocol/server: make listen backlog value as configurable) posted (#3) for review on master by mohammed rafi kc (rkavunga) REVIEW: https://review.gluster.org/17411 (protocol/server: make listen backlog value as configurable) posted (#4) for review on master by mohammed rafi kc (rkavunga) COMMIT: https://review.gluster.org/17411 committed in master by Jeff Darcy (jeff.us) ------ commit 0a20e56d07de3e467e09da885a6b71cdc165de17 Author: Mohammed Rafi KC <rkavunga> Date: Mon May 29 16:00:24 2017 +0530 protocol/server: make listen backlog value as configurable problem: When we call listen from protocol/server, we are giving a hard coded valie of 10 if it is not manually given. With multiplexing, especially when glusterd restarts all clients may try to connect to the server at a time. Which will result in overflowing the queue, and kernel will complain about the errors. Solution: This patch will introduce a volume set command to make backlog value as a configurable. This patch also changes the default values for backlog from 10 to 128. This changes is only applicable for sockets listening from protocol. Example: gluster volume set <volname> transport.listen-backlog 1024 Note: 1 Brick has to be restarted to get this value in effect 2 This changes won't be reflected in glusterd, or other xlators which calls listen. If you need, you have to add this option to the volfile. Change-Id: I0c5a2bbf28b5db612f9979e7560e05dd82b41477 BUG: 1456405 Signed-off-by: Mohammed Rafi KC <rkavunga> Reviewed-on: https://review.gluster.org/17411 Smoke: Gluster Build System <jenkins.org> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Reviewed-by: Raghavendra G <rgowdapp> Reviewed-by: Raghavendra Talur <rtalur> Reviewed-by: Atin Mukherjee <amukherj> Reviewed-by: Niels de Vos <ndevos> Reviewed-by: Jeff Darcy <jeff.us> 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.12.0, please open a new bug report. glusterfs-3.12.0 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/announce/2017-September/000082.html [2] https://www.gluster.org/pipermail/gluster-users/ |