Github user JessicaLHartog commented on the issue:
https://github.com/apache/storm/pull/2433
@danny0405 @revans2 Thanks for keeping the Storm on Mesos project in mind.
We (@erikdw, @srishtyagrawal, and myself) appreciate it!
Right now, Storm on Mesos doesn't work for Storm versions 1.1.x and above
because we rely on the slot-centric scheduling instead of the now
supervisor-centric scheduling (for more details see
[STORM-2126](https://issues.apache.org/jira/browse/STORM-2126)). We talked to
@revans2 about this in our
issue[#222](https://github.com/mesos/storm/issues/222#issuecomment-352514556)...
so that's a bit of context that may be necessary to understand the problem a
little better.
With respect to the ask to not further break Storm on Mesos we think it
would be best for us to be able to specify (at runtime) to the supervisor which
port it needs to listen on for these heartbeat messages. The way we see it,
while the Supervisor being able to specify a range for the heartbeat port
sounds like it may work, the Supervisor should _also_ be able to accept an
assigned heartbeat port. Namely, once we adapt to the changes suggested
[here](https://github.com/mesos/storm/issues/222#issuecomment-352530608), we
can start each Supervisor using one of the ports Mesos offers to us.
---
