Github user danny0405 commented on the issue:
https://github.com/apache/storm/pull/2433
@HeartSaVioR @erikdw
Yeah, `-c supervisor.thrift.port=<port>` will works great for starting
supervisor on Mesos.
My consideration is the workers started by parent supervisor, how do the
workers know it's parent heartbeat port? If i passed it as starting argument,
the port will be invalid if its parent supervisor collapse or restarts.
So who will maintain the consistency of heartbeats port for workers' parent
supervisor ?
---
