[
https://issues.apache.org/jira/browse/SLIDER-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271661#comment-15271661
]
Jonathan Maron commented on SLIDER-1117:
----------------------------------------
I can't off hand think of a current mechanism that would support that ability.
We probably either have to update the agent code to eliminate ports from the
range as they get assigned to port config items, or perhaps address this thru
configuration (e.g. define port ranges that can then be assigned to ports).
> Slider assigns same port to the component when we specify a range.
> ------------------------------------------------------------------
>
> Key: SLIDER-1117
> URL: https://issues.apache.org/jira/browse/SLIDER-1117
> Project: Slider
> Issue Type: Bug
> Components: appmaster
> Affects Versions: Slider 0.81
> Reporter: Seetharama Khandrika
> Priority: Critical
> Attachments: appConfig.json
>
>
> We are using slider to start and monitor elasticsearch in Yarn.
> The deployment works fine when we do not specify Port Range to slider using
> "site.global.slider.allowed.ports". However, when we specify port range, it
> gives the same port to both master_http_Port and master_tcp_port.
> I am attaching the appConfig.json that we used for deploying elasticsearch.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
