You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@mesos.apache.org by "Christoph Neuroth (JIRA)" <ji...@apache.org> on 2015/01/26 12:32:34 UTC
[jira] [Updated] (MESOS-2269) some tasks don't have a timestamp
[ https://issues.apache.org/jira/browse/MESOS-2269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Christoph Neuroth updated MESOS-2269:
-------------------------------------
Description:
(update: original bug report said this only affects failed tasks, but we're also seeing killed tasks with the empty state array)
For some failed or killed tasks in our mesos cluster, the JSON returned by the API contains an empty array:
{code:javascript}
state: "TASK_FAILED",
statuses: [ ]
{code}
While most tasks have at least two entries in the `statuses` field:
{code:javascript}
state: "TASK_KILLED",
statuses: [
{ state: "TASK_RUNNING", timestamp: 1421485535.89169 },
{ state: "TASK_KILLED", timestamp: 1421485603.19879 }
]
{code}
This makes the task list in the web UI hard to use because those failed tasks will always be shown first when sorting by timestamp and it's generally confusing to have tasks without timestamps.
was:
(update: original bug report said this only affects failed tasks, but we're also seeing killed tasks empty state array)
For some failed or killed tasks in our mesos cluster, the JSON returned by the API contains an empty array:
{code:javascript}
state: "TASK_FAILED",
statuses: [ ]
{code}
While most tasks have at least two entries in the `statuses` field:
{code:javascript}
state: "TASK_KILLED",
statuses: [
{ state: "TASK_RUNNING", timestamp: 1421485535.89169 },
{ state: "TASK_KILLED", timestamp: 1421485603.19879 }
]
{code}
This makes the task list in the web UI hard to use because those failed tasks will always be shown first when sorting by timestamp and it's generally confusing to have tasks without timestamps.
> some tasks don't have a timestamp
> ---------------------------------
>
> Key: MESOS-2269
> URL: https://issues.apache.org/jira/browse/MESOS-2269
> Project: Mesos
> Issue Type: Bug
> Components: json api
> Affects Versions: 0.20.1
> Reporter: Christoph Neuroth
>
> (update: original bug report said this only affects failed tasks, but we're also seeing killed tasks with the empty state array)
> For some failed or killed tasks in our mesos cluster, the JSON returned by the API contains an empty array:
> {code:javascript}
> state: "TASK_FAILED",
> statuses: [ ]
> {code}
> While most tasks have at least two entries in the `statuses` field:
> {code:javascript}
> state: "TASK_KILLED",
> statuses: [
> { state: "TASK_RUNNING", timestamp: 1421485535.89169 },
> { state: "TASK_KILLED", timestamp: 1421485603.19879 }
> ]
> {code}
> This makes the task list in the web UI hard to use because those failed tasks will always be shown first when sorting by timestamp and it's generally confusing to have tasks without timestamps.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)