On Wed, Feb 4, 2015 at 12:22 PM, David Kesler <[email protected]> wrote:
> I've posted this as an issue in marathon's github ( > https://github.com/mesosphere/marathon/issues/1140), but I also wanted to > post here as it may be an issue that mesos seems to not be handling the > case where it cannot successfully connect to a framework. (Obviously mesos > handling this better wouldn't fix the issues that crop up in marathon, but > it'd be nice if mesos gave some indication that it's not actually able to > successfully communicate with a framework. > > > > David. This is an artifact of Mesos (master) needing bi-directional communication between itself and framework scheduler, i.e., scheduler --> master and master --> scheduler should both work. As for the UI, agreed that it is a bit unintuitive. It lists a framework as "Terminated" only after failover timeout has elapsed. Feel free to file a ticket to fix that.
