[
https://issues.apache.org/jira/browse/STORM-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xiajun updated STORM-564:
-------------------------
Description:
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.
was:
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.
> 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)
