Details
Description
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.
Attachments
Issue Links
- is related to
-
MESOS-9667 Check failure when executor for task using resource provider resources subscribes before agent is registered
- Resolved
-
MESOS-7554 Add re-registration timeout for local resource providers
- Open
- relates to
-
MESOS-8467 Destroyed executors might be used after `Slave::publishResource()`.
- Resolved