[
https://issues.apache.org/jira/browse/SLIDER-1117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15271355#comment-15271355
]
Seetharama Khandrika commented on SLIDER-1117:
----------------------------------------------
We tried it with both single node cluster and multi node cluster and both
returned the same issues.
In the appConfig.json, I am using the same ${ES_MASTER.ALLOCATED_PORT} to both
TCP and HTTP ports.
When I do not specify the range, it gives the same port for
${ES_MASTER.ALLOCATED_PORT}.
When I do not specify the port range, it give different ports for
${ES_MASTER.ALLOCATED_PORT} when used against HTTP Port and TCP Port.
> 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)
