[
https://issues.apache.org/jira/browse/MESOS-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15359609#comment-15359609
]
Vinod Kone commented on MESOS-5761:
-----------------------------------
Lets keep this ticket focused on how to let the master know about
FrameworkInfos for these orphan tasks.
I see 2 options
1) Agent providing this information during Reregistration. This is relatively
easy to implement.
2) Persist framework infos in the registry. This is more involved. But we need
this anyway and once we have this, we wouldn't need above.
> Improve the logic of orphan tasks
> ---------------------------------
>
> Key: MESOS-5761
> URL: https://issues.apache.org/jira/browse/MESOS-5761
> Project: Mesos
> Issue Type: Bug
> Reporter: Joerg Schad
> Assignee: Joerg Schad
>
> Right now, a task is called orphaned if an agent re-registers with it but the
> corresponding framework information is not known to the master. This happens
> immediately after a master failover.
> It would great if the master knows the information about the framework even
> after a failover, irrespective of whether a framework re-registers, so that
> we don't have orphan tasks. Getting rid of orphan tasks will make the task
> authorization story easy (see MESOS-5757).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
