[
https://issues.apache.org/jira/browse/STORM-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14224002#comment-14224002
]
ASF GitHub Bot commented on STORM-564:
--------------------------------------
Github user tedxia commented on the pull request:
https://github.com/apache/storm/pull/322#issuecomment-64305974
@nathanmarz If I run storm on yarn or mesos, it is not easy to find a
unique set of free ports, just as other service that scheduled by yarn or mesos
use dynamic port. Worker user dynamic port also enable user use deploy it's own
storm cluster as yarn's signal app, and we treat the cluster as a whole
resource poll, use yarn to achieve resource management.
> Support worker use dynamic port
> -------------------------------
>
> Key: STORM-564
> URL: https://issues.apache.org/jira/browse/STORM-564
> Project: Apache Storm
> Issue Type: Improvement
> Affects Versions: 0.10.0
> Reporter: xiajun
> Assignee: xiajun
> Priority: Minor
>
> Background: When deploy storm mixed with other services, or deploy storm by
> yarn and mesos or some other scheduling system, worker port conflict is
> really a big problem.
> In order to fix this, we add worker.dynamic.port to indicate whether worker
> bind dynamic port or not.
> When set worker.dynamic.port as true, worker will use port that specified by
> supervisor.slots.ports;
> When set worker.dynamic.port as false, worker will bind 0, and the port that
> specified by supervisor.slots.ports will be nominally port in storm, which
> stand for worker really bind port.
> And when worker launched, worker will report it's really bind port by
> heartbeat, and nimbus send worker's bind port by assignment.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
