You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Vinod Kone (JIRA)" <ji...@apache.org> on 2016/07/01 20:49:11 UTC
[jira] [Updated] (MESOS-5761) Improve the logic of orphan tasks
[ https://issues.apache.org/jira/browse/MESOS-5761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vinod Kone updated MESOS-5761:
------------------------------
Description:
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).
was:Currently, we don't filter orphaned tasks based on user authorization. This can potentially expose sensitive information to users.
Summary: Improve the logic of orphan tasks (was: Filter orphaned task from /state.)
> 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)