[jira] [Updated] (MESOS-6171) Introduce "global" decision policy for unhealthy tasks.
[ https://issues.apache.org/jira/browse/MESOS-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Rukletsov updated MESOS-6171: --- Sprint: Mesosphere Sprint 44 (was: Mesosphere Sprint 44, Mesosphere Sprint 45) > Introduce "global" decision policy for unhealthy tasks. > --- > > Key: MESOS-6171 > URL: https://issues.apache.org/jira/browse/MESOS-6171 > Project: Mesos > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Alexander Rukletsov >Assignee: haosdent > Labels: health-check, mesosphere > > Currently, if the task is deemed unhealthy, i.e. it failed a health check a > certain number of times, it is killed by both default executors: > [command|https://github.com/apache/mesos/blob/b053572bc424478cafcd60d1bce078f5132c4590/src/launcher/executor.cpp#L299] > and > [docker|https://github.com/apache/mesos/blob/b053572bc424478cafcd60d1bce078f5132c4590/src/docker/executor.cpp#L315]. > This is what can be called "local" kill policy. > While local kill policy can save some network traffic and unload the > scheduler, there are cases, when a scheduler may want to decide what—and > when—to do. This is what can be called "global" policy, i.e. the health check > library reports whether a health check failed or succeeded, while the > executor forwards this update to the scheduler without taking any action. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-6171) Introduce "global" decision policy for unhealthy tasks.
[ https://issues.apache.org/jira/browse/MESOS-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vinod Kone updated MESOS-6171: -- Sprint: Mesosphere Sprint 44, Mesosphere Sprint 45 (was: Mesosphere Sprint 44) > Introduce "global" decision policy for unhealthy tasks. > --- > > Key: MESOS-6171 > URL: https://issues.apache.org/jira/browse/MESOS-6171 > Project: Mesos > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Alexander Rukletsov >Assignee: haosdent > Labels: health-check, mesosphere > > Currently, if the task is deemed unhealthy, i.e. it failed a health check a > certain number of times, it is killed by both default executors: > [command|https://github.com/apache/mesos/blob/b053572bc424478cafcd60d1bce078f5132c4590/src/launcher/executor.cpp#L299] > and > [docker|https://github.com/apache/mesos/blob/b053572bc424478cafcd60d1bce078f5132c4590/src/docker/executor.cpp#L315]. > This is what can be called "local" kill policy. > While local kill policy can save some network traffic and unload the > scheduler, there are cases, when a scheduler may want to decide what—and > when—to do. This is what can be called "global" policy, i.e. the health check > library reports whether a health check failed or succeeded, while the > executor forwards this update to the scheduler without taking any action. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MESOS-6171) Introduce "global" decision policy for unhealthy tasks.
[ https://issues.apache.org/jira/browse/MESOS-6171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gastón Kleiman updated MESOS-6171: -- Sprint: Mesosphere Sprint 44 > Introduce "global" decision policy for unhealthy tasks. > --- > > Key: MESOS-6171 > URL: https://issues.apache.org/jira/browse/MESOS-6171 > Project: Mesos > Issue Type: Improvement >Affects Versions: 1.0.0 >Reporter: Alexander Rukletsov >Assignee: haosdent > Labels: health-check, mesosphere > > Currently, if the task is deemed unhealthy, i.e. it failed a health check a > certain number of times, it is killed by both default executors: > [command|https://github.com/apache/mesos/blob/b053572bc424478cafcd60d1bce078f5132c4590/src/launcher/executor.cpp#L299] > and > [docker|https://github.com/apache/mesos/blob/b053572bc424478cafcd60d1bce078f5132c4590/src/docker/executor.cpp#L315]. > This is what can be called "local" kill policy. > While local kill policy can save some network traffic and unload the > scheduler, there are cases, when a scheduler may want to decide what—and > when—to do. This is what can be called "global" policy, i.e. the health check > library reports whether a health check failed or succeeded, while the > executor forwards this update to the scheduler without taking any action. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
