Bug 1474745
| Summary: | [RFE] Reserved port range for Gluster | |||
|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Raghavendra Talur <rtalur> | |
| Component: | glusterd | Assignee: | Atin Mukherjee <amukherj> | |
| Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> | |
| Severity: | high | Docs Contact: | ||
| Priority: | low | |||
| Version: | rhgs-3.3 | CC: | amukherj, annair, hchiramm, jkaur, madam, nchilaka, rhinduja, rhs-bugs, rtalur, sankarshan, sheggodu, srmukher, storage-qa-internal, vbellur | |
| Target Milestone: | --- | Keywords: | FutureFeature | |
| Target Release: | RHGS 3.4.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | glusterfs-3.12.2-1 | Doc Type: | Enhancement | |
| Doc Text: |
Red Hat Gluster Storage 3.4 allows you to define the max port value in glusterd.vol to control the range of port that gluster bricks can consume.
|
Story Points: | --- | |
| Clone Of: | 1458646 | |||
| : | 1531937 (view as bug list) | Environment: | ||
| Last Closed: | 2018-09-04 06:34:19 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: | 1458646, 1472361, 1503132, 1503135, 1531937 | |||
|
Comment 4
Atin Mukherjee
2017-08-10 13:20:17 UTC
Build: 3.12.2-5 Set the max port number as 49200 in the /etc/glusterfs/glusterd.vol, restarted glusterd to get the changes reflected from the glusterd.vol file. glusterd should not be able to allocate the port beyond the max port range when the port number exceeds the limit set in the vol file, the volume start will fail as below [root@dhcp37-54 ~]# gluster vol start testvol_z volume start: testvol_z: failed: Commit failed on localhost. Please check log file for details Glusterd log saying all the ports are exhausted [2018-03-13 09:07:42.855879] E [MSGID: 106612] [glusterd-utils.c:2016:glusterd_volume_start_glusterfs] 0-management: All the ports in the range are exhausted, can't start brick /bricks/brick0/testvol_100z for volume testvol_z comment out the max-port in glusterd.vol file and restart glusterd. Now the default max port is set to 65535. Now volume start succeeds [root@dhcp37-54 ~]# gluster vol start testvol_z volume start: testvol_z: success Hence marking it as verified Updated the doc text. Kindly review and confirm Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2018:2607 |