You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@mesos.apache.org by Tomek Janiszewski <ja...@gmail.com> on 2016/12/09 10:27:08 UTC
Command healthcheck failed but status KILLED
Hi
What is desired behavior when command health check failed? On Mesos 1.0.2
when health check fails task has state KILLED instead of FAILED with reason
specifying it was killed due to failing health check.
Thanks
Tomek
Re: Command healthcheck failed but status KILLED
Posted by Tomek Janiszewski <ja...@gmail.com>.
Thanks Gastón. Do we have a shepherd for this? It's not critical but make
it hard to distinguish task killed by failed health check from killed by
scheduler.
wt., 13.12.2016 o 16:55 użytkownik Gastón Kleiman <ga...@mesosphere.io>
napisał:
> On Mon, Dec 12, 2016 at 12:47 PM, Tomek Janiszewski <ja...@gmail.com>
> wrote:
>
> > It there any information that kill is the result of failed healthcheck?
> > TaskHealthStatus should have some details on what was wrong. When default
> > executor is killing task it should add a reason and details to
> TaskStatus.
> > What do you think?
> >
>
> I agree with you, so I created
> https://issues.apache.org/jira/browse/MESOS-6786 with some ideas.
>
> -Gastón
>
Re: Command healthcheck failed but status KILLED
Posted by Tomek Janiszewski <ja...@gmail.com>.
Thanks Gastón. Do we have a shepherd for this? It's not critical but make
it hard to distinguish task killed by failed health check from killed by
scheduler.
wt., 13.12.2016 o 16:55 użytkownik Gastón Kleiman <ga...@mesosphere.io>
napisał:
> On Mon, Dec 12, 2016 at 12:47 PM, Tomek Janiszewski <ja...@gmail.com>
> wrote:
>
> > It there any information that kill is the result of failed healthcheck?
> > TaskHealthStatus should have some details on what was wrong. When default
> > executor is killing task it should add a reason and details to
> TaskStatus.
> > What do you think?
> >
>
> I agree with you, so I created
> https://issues.apache.org/jira/browse/MESOS-6786 with some ideas.
>
> -Gastón
>
Re: Command healthcheck failed but status KILLED
Posted by Gastón Kleiman <ga...@mesosphere.io>.
On Mon, Dec 12, 2016 at 12:47 PM, Tomek Janiszewski <ja...@gmail.com>
wrote:
> It there any information that kill is the result of failed healthcheck?
> TaskHealthStatus should have some details on what was wrong. When default
> executor is killing task it should add a reason and details to TaskStatus.
> What do you think?
>
I agree with you, so I created
https://issues.apache.org/jira/browse/MESOS-6786 with some ideas.
-Gastón
Re: Command healthcheck failed but status KILLED
Posted by Gastón Kleiman <ga...@mesosphere.io>.
On Mon, Dec 12, 2016 at 12:47 PM, Tomek Janiszewski <ja...@gmail.com>
wrote:
> It there any information that kill is the result of failed healthcheck?
> TaskHealthStatus should have some details on what was wrong. When default
> executor is killing task it should add a reason and details to TaskStatus.
> What do you think?
>
I agree with you, so I created
https://issues.apache.org/jira/browse/MESOS-6786 with some ideas.
-Gastón
Re: Command healthcheck failed but status KILLED
Posted by Tomek Janiszewski <ja...@gmail.com>.
It there any information that kill is the result of failed healthcheck?
TaskHealthStatus should have some details on what was wrong. When default
executor is killing task it should add a reason and details to TaskStatus.
What do you think?
pon., 12.12.2016 o 11:11 użytkownik Alex Rukletsov <al...@mesosphere.com>
napisał:
> Technically the task hast not failed but was killed by the executor
> (because it failed a health check).
>
> On Fri, Dec 9, 2016 at 11:27 AM, Tomek Janiszewski <ja...@gmail.com>
> wrote:
>
> > Hi
> >
> > What is desired behavior when command health check failed? On Mesos 1.0.2
> > when health check fails task has state KILLED instead of FAILED with
> reason
> > specifying it was killed due to failing health check.
> >
> > Thanks
> > Tomek
> >
>
Re: Command healthcheck failed but status KILLED
Posted by Tomek Janiszewski <ja...@gmail.com>.
It there any information that kill is the result of failed healthcheck?
TaskHealthStatus should have some details on what was wrong. When default
executor is killing task it should add a reason and details to TaskStatus.
What do you think?
pon., 12.12.2016 o 11:11 użytkownik Alex Rukletsov <al...@mesosphere.com>
napisał:
> Technically the task hast not failed but was killed by the executor
> (because it failed a health check).
>
> On Fri, Dec 9, 2016 at 11:27 AM, Tomek Janiszewski <ja...@gmail.com>
> wrote:
>
> > Hi
> >
> > What is desired behavior when command health check failed? On Mesos 1.0.2
> > when health check fails task has state KILLED instead of FAILED with
> reason
> > specifying it was killed due to failing health check.
> >
> > Thanks
> > Tomek
> >
>
Re: Command healthcheck failed but status KILLED
Posted by Alex Rukletsov <al...@mesosphere.com>.
Technically the task hast not failed but was killed by the executor
(because it failed a health check).
On Fri, Dec 9, 2016 at 11:27 AM, Tomek Janiszewski <ja...@gmail.com>
wrote:
> Hi
>
> What is desired behavior when command health check failed? On Mesos 1.0.2
> when health check fails task has state KILLED instead of FAILED with reason
> specifying it was killed due to failing health check.
>
> Thanks
> Tomek
>
Re: Command healthcheck failed but status KILLED
Posted by Alex Rukletsov <al...@mesosphere.com>.
Technically the task hast not failed but was killed by the executor
(because it failed a health check).
On Fri, Dec 9, 2016 at 11:27 AM, Tomek Janiszewski <ja...@gmail.com>
wrote:
> Hi
>
> What is desired behavior when command health check failed? On Mesos 1.0.2
> when health check fails task has state KILLED instead of FAILED with reason
> specifying it was killed due to failing health check.
>
> Thanks
> Tomek
>