[
https://issues.apache.org/jira/browse/MESOS-9711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16813923#comment-16813923
]
Chun-Hung Hsiao commented on MESOS-9711:
----------------------------------------
It might not be optimal to defer that. It seems to me that it would be better
if executor reregistration doesn't rely on resource publishing, as suggested in
https://issues.apache.org/jira/browse/MESOS-9667?focusedCommentId=16805529&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16805529
> Avoid shutting down executors registering before a required resource provider
> -----------------------------------------------------------------------------
>
> Key: MESOS-9711
> URL: https://issues.apache.org/jira/browse/MESOS-9711
> Project: Mesos
> Issue Type: Improvement
> Components: agent
> Affects Versions: 1.8.0
> Reporter: Benjamin Bannier
> Priority: Critical
> Labels: agent, mesosphere, provider, storage
>
> If an HTTP-based executor resubscribes after agent failover before a resource
> provider exposing some of its resources has subscribed itself the agent
> currently does not know how to inform the resource provider about the
> existing resource user and shuts the executor down.
> This is not optimal as the resource provider might subscribe soon, but we
> fail the task nevertheless.
> We should consider improving on that, e.g., by deferring executor
> subscription until all providers have resubscribed or their registration
> timeout is reached, see MESOS-7554.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
