[jira] [Updated] (MESOS-1930) Expose TASK_KILLED reason.

2015-08-18 Thread Greg Mann (JIRA)

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

Greg Mann updated MESOS-1930:
-
Assignee: (was: Dominic Hamon)

 Expose TASK_KILLED reason.
 --

 Key: MESOS-1930
 URL: https://issues.apache.org/jira/browse/MESOS-1930
 Project: Mesos
  Issue Type: Story
Reporter: Alexander Rukletsov
Priority: Minor

 A task process may be killed by a SIGTERM or SIGKILL. The only possibility to 
 check how the task process has exited is to examine the message: 
 {{status.message().find(Terminated)}}. However, a task may not run in its 
 own process, hence the executor may not be able to provide an exit status. 
 What we actually want is an artificial task exit status that is rendered by 
 the executor.
 This may be resolved by adding second tier states or state explanations. Here 
 is a link to a discussion: https://reviews.apache.org/r/26382/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (MESOS-1930) Expose TASK_KILLED reason.

2014-11-17 Thread Dominic Hamon (JIRA)

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

Dominic Hamon updated MESOS-1930:
-
Sprint: Twitter Mesos Q4 Sprint 2, Twitter Mesos Q4 Sprint 3, Twitter Mesos 
Q4 Sprint 4  (was: Twitter Mesos Q4 Sprint 2, Twitter Mesos Q4 Sprint 3)

 Expose TASK_KILLED reason.
 --

 Key: MESOS-1930
 URL: https://issues.apache.org/jira/browse/MESOS-1930
 Project: Mesos
  Issue Type: Story
Reporter: Alexander Rukletsov
Assignee: Dominic Hamon
Priority: Minor

 A task process may be killed by a SIGTERM or SIGKILL. The only possibility to 
 check how the task process has exited is to examine the message: 
 {{status.message().find(Terminated)}}. However, a task may not run in its 
 own process, hence the executor may not be able to provide an exit status. 
 What we actually want is an artificial task exit status that is rendered by 
 the executor.
 This may be resolved by adding second tier states or state explanations. Here 
 is a link to a discussion: https://reviews.apache.org/r/26382/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (MESOS-1930) Expose TASK_KILLED reason.

2014-11-17 Thread Dominic Hamon (JIRA)

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

Dominic Hamon updated MESOS-1930:
-
Sprint: Twitter Mesos Q4 Sprint 2, Twitter Mesos Q4 Sprint 3  (was: Twitter 
Mesos Q4 Sprint 2, Twitter Mesos Q4 Sprint 3, Twitter Mesos Q4 Sprint 4)

 Expose TASK_KILLED reason.
 --

 Key: MESOS-1930
 URL: https://issues.apache.org/jira/browse/MESOS-1930
 Project: Mesos
  Issue Type: Story
Reporter: Alexander Rukletsov
Assignee: Dominic Hamon
Priority: Minor

 A task process may be killed by a SIGTERM or SIGKILL. The only possibility to 
 check how the task process has exited is to examine the message: 
 {{status.message().find(Terminated)}}. However, a task may not run in its 
 own process, hence the executor may not be able to provide an exit status. 
 What we actually want is an artificial task exit status that is rendered by 
 the executor.
 This may be resolved by adding second tier states or state explanations. Here 
 is a link to a discussion: https://reviews.apache.org/r/26382/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (MESOS-1930) Expose TASK_KILLED reason.

2014-11-03 Thread Dominic Hamon (JIRA)

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

Dominic Hamon updated MESOS-1930:
-
Sprint: Twitter Mesos Q4 Sprint 2, Twitter Mesos Q4 Sprint 3  (was: Twitter 
Mesos Q4 Sprint 2)

 Expose TASK_KILLED reason.
 --

 Key: MESOS-1930
 URL: https://issues.apache.org/jira/browse/MESOS-1930
 Project: Mesos
  Issue Type: Story
Reporter: Alexander Rukletsov
Assignee: Dominic Hamon
Priority: Minor

 A task process may be killed by a SIGTERM or SIGKILL. The only possibility to 
 check how the task process has exited is to examine the message: 
 {{status.message().find(Terminated)}}. However, a task may not run in its 
 own process, hence the executor may not be able to provide an exit status. 
 What we actually want is an artificial task exit status that is rendered by 
 the executor.
 This may be resolved by adding second tier states or state explanations. Here 
 is a link to a discussion: https://reviews.apache.org/r/26382/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (MESOS-1930) Expose TASK_KILLED reason.

2014-10-20 Thread Dominic Hamon (JIRA)

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

Dominic Hamon updated MESOS-1930:
-
Sprint: Twitter Q4 Sprint 2

 Expose TASK_KILLED reason.
 --

 Key: MESOS-1930
 URL: https://issues.apache.org/jira/browse/MESOS-1930
 Project: Mesos
  Issue Type: Story
Reporter: Alexander Rukletsov
Assignee: Dominic Hamon
Priority: Minor

 A task process may be killed by a SIGTERM or SIGKILL. The only possibility to 
 check how the task process has exited is to examine the message: 
 {{status.message().find(Terminated)}}. However, a task may not run in its 
 own process, hence the executor may not be able to provide an exit status. 
 What we actually want is an artificial task exit status that is rendered by 
 the executor.
 This may be resolved by adding second tier states or state explanations. Here 
 is a link to a discussion: https://reviews.apache.org/r/26382/



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)