Filed https://issues.apache.org/jira/browse/SLIDER-1137
On Wed, Jun 1, 2016 at 9:25 AM, Jon Maron <[email protected]> wrote: > I certainly would go ahead and file a JIRA. The two sound essentially > synonymous - the per component setting would allow for distinguishing those > elements that actually get assigned ports from the specified ranges. > > > On Jun 1, 2016, at 12:15 PM, Manoj Samel <[email protected]> > wrote: > > > > Any thoughts ? > > > > On Wed, May 25, 2016 at 11:27 AM, Manoj Samel <[email protected]> > > wrote: > > > >> Hi, > >> > >> At present the allowed.ports is applied to AM as well as containers > >> > >> While this may be a valid use case for certain deployments, there are > >> other use cases > >> > >> 1. The "allowed.ports" should be only applied to certain port(s) for > >> components that are marked as {ALLOCATED_PORT}{PER_CONTAINER} etc.. The > >> components expose certain end points to clients outside the firewall. > Only > >> those end points should be controlled by allowed.ports. All ports used > by > >> AM and containers internal apps should use any available port outside > the > >> allowed.ports range since in this case, the AM and containers are within > >> same firewall zone. This will reduce unnecessary usage of ports that are > >> open to firewall > >> > >> 2. Somewhat related to #1, the allowed.port is a global setting right > now. > >> It would be really useful to have a option to specify it per component. > >> E.g. if different components are serving different customers; it would > be > >> great to have a port range specific to a component > >> > >> Any thoughts ? Should I file a enhancement Jira ? > >> > >> Thanks, > >> > >
