Github user tedxia commented on the pull request:
https://github.com/apache/storm/pull/322#issuecomment-64528627
I read [storm-mesos](https://github.com/mesos/storm) just now and know how
it works. It easy for storm on mesos because mesos support offer port while
yarn don't. Thank to
Github user tedxia closed the pull request at:
https://github.com/apache/storm/pull/322
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Github user nathanmarz commented on the pull request:
https://github.com/apache/storm/pull/322#issuecomment-64515204
Storm's ISupervisor / INimbus interfaces let you control port assignment
external to Storm itself. I don't know about YARN, but that's how I got
storm-mesos working. Th
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. Work
Github user nathanmarz commented on the pull request:
https://github.com/apache/storm/pull/322#issuecomment-64305199
-1. Why don't you just set the port configuration on those nodes to a
unique set of ports that won't conflict with other services?
---
If your project is set up for it
Github user tedxia commented on the pull request:
https://github.com/apache/storm/pull/322#issuecomment-64302867
This PR is similar to
[STORM-253](https://issues.apache.org/jira/browse/STORM-253), but use different
solution, @clockfly can you have a look at this, thank you.
---
If
GitHub user tedxia opened a pull request:
https://github.com/apache/storm/pull/322
STORM-564: Worker use dynamic port
PR for STORM-564
The main change are:
1. Add worker.dynamic.port to indicate whether worker bind dynamic port or
not;
2. Add node+port->bind-port i
