You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@tez.apache.org by "Eric Wohlstadter (JIRA)" <ji...@apache.org> on 2018/10/26 05:00:00 UTC
[jira] [Commented] (TEZ-3957) Report TASK_DURATION_MILLIS as a
Counter for completed tasks
[ https://issues.apache.org/jira/browse/TEZ-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664655#comment-16664655 ]
Eric Wohlstadter commented on TEZ-3957:
---------------------------------------
[~sershe]
Do you want the counter to be continuously updated and reported back to the AM from running task containers?
I was planning to just add the counter at DAG completion time, from information in the AM about completed tasks. That's what I meant by "Report TASK_DURATION_MILLIS as a Counter for completed tasks".
What I had in mind is less useful in general than what I understand this patch is doing, but it doesn't add any overhead to AM <-> Container messaging.
Wanted to check that there is a use-case where having this as a running counter is useful (it wasn't necessary for my use-case).
> Report TASK_DURATION_MILLIS as a Counter for completed tasks
> ------------------------------------------------------------
>
> Key: TEZ-3957
> URL: https://issues.apache.org/jira/browse/TEZ-3957
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Eric Wohlstadter
> Assignee: Sergey Shelukhin
> Priority: Major
> Attachments: TEZ-3957.patch
>
>
> timeTaken is already being reported by {{TaskAttemptFinishedEvent}}, but not as a Counter.
> Combined with TEZ-3911, this provides min(timeTaken), max(timeTaken), avg(timeTaken).
> The value will be: {{finishTime - launchTime}}
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)