[
https://issues.apache.org/jira/browse/MESOS-1550?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14046397#comment-14046397
]
Bill Farner commented on MESOS-1550:
------------------------------------
Somewhat related, does it make sense to also follow up with an API
change/deprecation to make the behavior of {{stop()}} more obvious (i.e. rename
the method)? Aurora also bumped into the unintended consequences years ago,
and i doubt we were the last.
> MesosSchedulerDriver should never, ever, call 'stop'.
> -----------------------------------------------------
>
> Key: MESOS-1550
> URL: https://issues.apache.org/jira/browse/MESOS-1550
> Project: Mesos
> Issue Type: Bug
> Components: framework, java api, python api
> Affects Versions: 0.14.0, 0.14.1, 0.14.2, 0.17.0, 0.16.0, 0.15.0, 0.18.0,
> 0.19.0
> Reporter: Benjamin Hindman
> Priority: Critical
> Fix For: 0.19.1
>
>
> Using MesosSchedulerDriver.stop causes the master to unregister the
> framework. The library should never make this decision for a framework, it
> should defer to the framework itself.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
