Github user erikdw commented on the issue:
https://github.com/apache/storm/pull/2433
/quote My consideration is the workers started by parent supervisor, how do
the workers know their parent supervisor's heartbeat/assignment port? If i
passed it as starting argument, the port will be invalid if its parent
supervisor collapse or restarts.
For storm-on-mesos, the Supervisor + Workers run in a per-topology
container on each host. The Supervisor is the container's init process, so if
it dies then the Workers die with it. So the problematic scenario you outlined
doesn't exist for that use-case.
---
