[
https://issues.apache.org/jira/browse/MESOS-6790?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16137636#comment-16137636
]
Gastón Kleiman edited comment on MESOS-6790 at 8/22/17 11:56 PM:
-----------------------------------------------------------------
We discussed this briefly with [~vinodkone] and [~greggomann].
The consensus was that to fully solve this problem we should probably do both
things:
1. Add (and checkpoint) a {{start_time}} field.
2. Make the build-in executors send {{TASK_STARTING}} updates.
Sending the {{TASK_STARTING}} update approach is not enough because it might be
lost after a master failover.
We should be careful when updating the built-in executors. Even though the
state exists since the dawn of Mesos, some schedulers might not be able to
handle them in the right way, e.g., Chronos:
https://github.com/mesos/chronos/blob/3758d2c1ab4f517a21bd7d7c0488540cbecc2fc0/src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosJobFramework.scala#L199-L208
was (Author: gkleiman):
We discussed this briefly with @vinodkone and @greg.
The consensus was that to fully solve this problem we should probably do both
things:
1. Add (and checkpoint) a {{start_time}} field.
2. Make the build-in executors send {{TASK_STARTING}} updates.
Sending the {{TASK_STARTING}} update approach is not enough because it might be
lost after a master failover.
We should be careful when updating the built-in executors. Even though the
state exists since the dawn of Mesos, some schedulers might not be able to
handle them in the right way, e.g., Chronos:
https://github.com/mesos/chronos/blob/3758d2c1ab4f517a21bd7d7c0488540cbecc2fc0/src/main/scala/org/apache/mesos/chronos/scheduler/mesos/MesosJobFramework.scala#L199-L208
> Wrong task started time in webui
> --------------------------------
>
> Key: MESOS-6790
> URL: https://issues.apache.org/jira/browse/MESOS-6790
> Project: Mesos
> Issue Type: Bug
> Components: webui
> Reporter: haosdent
> Assignee: Tomasz Janiszewski
> Labels: health-check, mesosphere, observability, webui
>
> Reported by [~janisz]
> {quote}
> Hi
> When task has enabled Mesos healthcheck start time in UI can show wrong
> time. This happens because UI assumes that first status is task started
> [0]. This is not always true because Mesos keeps only recent tasks statuses
> [1] so when healthcheck updates tasks status it can override task start
> time displayed in webui.
> Best
> Tomek
> [0]
> https://github.com/apache/mesos/blob/master/src/webui/master/static/js/controllers.js#L140
> [1]
> https://github.com/apache/mesos/blob/f2adc8a95afda943f6a10e771aad64300da19047/src/common/protobuf_utils.cpp#L263-L265
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
