Bug 1460597
| Summary: | [RFE][GSS]Gluster process should use ports above reserved ports (above 1023) | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Abhishek Kumar <abhishku> |
| Component: | core | Assignee: | Bug Updates Notification Mailing List <rhs-bugs> |
| Status: | CLOSED DEFERRED | QA Contact: | Rahul Hinduja <rhinduja> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | rhgs-3.1 | CC: | abhishku, amukherj, atumball, bkunal, mchangir, mmahudha, mmalhotr, rhs-bugs, rtalur, sankarshan, skoduri, storage-qa-internal, vbellur |
| Target Milestone: | --- | Keywords: | FutureFeature, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-04-24 17:27: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: | 1408949, 1468976, 1472361 | ||
|
Description
Abhishek Kumar
2017-06-12 07:09:09 UTC
The problem mentioned in the original bug description about openshift and gluster trying to use same ports is a problem that can't be solved as it is the problem of limited resources and more demand. To fix the problem that is mentioned in comment 2 about gluster using a port that is used by rquotad, you can use the ip_local_reserved_ports feature of linux kernel as mentioned in https://www.kernel.org/doc/Documentation/networking/ip-sysctl.txt . We follow the same model that is used by linux kernel for port allocation. We don't bind to a port that is listed in the reserved ports list. Specifying 875 port in this list would ensure that gluster client processes don't use it. There is a certain trust logic in Gluster that requires binding to a port under 1024 and it will take a few more releases before we can completely get rid of it. This issue is not anything specific to GlusterD. Moving it to core. I spoke to Atin and others too. There is no way to do this in our current version. I still stand by my original answer that it is up to the admin to use ip_local_reserved_ports option to handle these errors and does not need any code change. Looks like we have the solution as per #c25 here. Should we do anything else? Or close this as FIXED? *** Bug 1294237 has been marked as a duplicate of this bug. *** > Do we have this behaviour clearly documented in our gluster docs ? and if not do we have a document Bz raised to document this behaviour ?
Bipin, adding a needinfo for you! If you think it is documented enough, feel free to close this!
Note that all the customer cases are now in Closed state at present!
Bipin, while I understand that there are many customer issues raised about this issue, the fix for this would involve major changes at n/w layer at present. Hence we are inclined towards closing this as DEFERRED (ie, will pick it up only if this gets scoped for future releases (!3.5, but beyond). Please check with PM on scoping and re-open if it gets prioritized from GSS. For now, our statement is same as comment#29, and hence we will close this as DEFERRED. |