mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jie Yu (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MESOS-7554) Add health check for resource providers
Date Wed, 03 Jan 2018 22:14:01 GMT

     [ https://issues.apache.org/jira/browse/MESOS-7554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jie Yu updated MESOS-7554:
--------------------------
    Description: Similar to master health checking agents, local resource providers need to
be health checked as well. This re-registration timeout will be started when a resource provider
seems to have disconnected, similar to how it's done for agents. While waiting for the resource
provider to reconnect, it will be deactivated. On re-registration the timeout will be canceled
and the resource provider activated again. In case of a timeout, the internal state will be
changed to {{unreachable}} (as it is for agents in that situation) and considered gone.  (was:
Similar to master health checking agents, resource providers need to be health checked as
well. This re-registration timeout will be started when a resource provider seems to have
disconnected, similar to how it's done for agents. While waiting for the resource provider
to reconnect, it will be deactivated. On re-registration the timeout will be canceled and
the resource provider activated again. In case of a timeout, the internal state will be changed
to {{unreachable}} (as it is for agents in that situation) and considered gone.)

> Add health check for resource providers
> ---------------------------------------
>
>                 Key: MESOS-7554
>                 URL: https://issues.apache.org/jira/browse/MESOS-7554
>             Project: Mesos
>          Issue Type: Task
>          Components: master
>            Reporter: Jan Schlicht
>              Labels: csi-post-mvp, mesosphere, storage
>
> Similar to master health checking agents, local resource providers need to be health
checked as well. This re-registration timeout will be started when a resource provider seems
to have disconnected, similar to how it's done for agents. While waiting for the resource
provider to reconnect, it will be deactivated. On re-registration the timeout will be canceled
and the resource provider activated again. In case of a timeout, the internal state will be
changed to {{unreachable}} (as it is for agents in that situation) and considered gone.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message