[
https://issues.apache.org/jira/browse/MESOS-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15555500#comment-15555500
]
Megha commented on MESOS-6223:
------------------------------
This jira came out as a pre-requisite to support task restart post a reboot.
There are definitely use cases where you would need a persistent agent Id
because resources like persistent volumes are not tied to the lifecycle of the
ephemeral agent and exist even after the agent is gone. But the thing is in
order to support task restart on the rebooted host we need the previous agent
Id or session Id (from MESOS-5368) to recover and figure out which tasks to
restart and restart them eventually. So, I believe the agent or session
recovery post a reboot is needed. I believe recovery being short-circuited
after reboot is an optimization because of the fact that no tasks/executors are
running after agent's host reboot which will change with MESOS-3545.
> Allow agents to re-register post a host reboot
> ----------------------------------------------
>
> Key: MESOS-6223
> URL: https://issues.apache.org/jira/browse/MESOS-6223
> Project: Mesos
> Issue Type: Improvement
> Components: slave
> Reporter: Megha
>
> Agent does’t recover its state post a host reboot, it registers with the
> master and gets a new SlaveID. With partition awareness, the agents are now
> allowed to re-register after they have been marked Unreachable. The executors
> are anyway terminated on the agent when it reboots so there is no harm in
> letting the agent keep its SlaveID, re-register with the master and reconcile
> the lost executors. This is a pre-requisite for supporting
> persistent/restartable tasks in mesos (MESOS-3545).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
