You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@storm.apache.org by "Rick Kellogg (JIRA)" <ji...@apache.org> on 2015/10/05 03:53:27 UTC
[jira] [Updated] (STORM-564) Support worker use dynamic port
[ https://issues.apache.org/jira/browse/STORM-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Kellogg updated STORM-564:
-------------------------------
Component/s: storm-core
> Support worker use dynamic port
> -------------------------------
>
> Key: STORM-564
> URL: https://issues.apache.org/jira/browse/STORM-564
> Project: Apache Storm
> Issue Type: Improvement
> Components: storm-core
> 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)