[
https://issues.apache.org/jira/browse/TEZ-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14741226#comment-14741226
]
Bikas Saha commented on TEZ-2810:
---------------------------------
Thanks for the review!
I am not expecting number of preemptions to be high. Also, when there are
multiple pending tasks causing multiple preemptions, we currently dont have any
connecting data in the events to pair them up. Given low number of preemptions
and no correlating data, I decided to err on the side of mentioning all
preemptions. In the common case this list will be small and will let us quickly
look at which attempts got preempted (in the critical path or for log search).
What I could do is consolidate them all in a single line. Will do that and
commit.
Thanks!
> Support for showing allocation delays due to internal preemption
> ----------------------------------------------------------------
>
> Key: TEZ-2810
> URL: https://issues.apache.org/jira/browse/TEZ-2810
> Project: Apache Tez
> Issue Type: Sub-task
> Reporter: Bikas Saha
> Assignee: Bikas Saha
> Attachments: TEZ-2810.1.patch, cp4-preempt-1.png, cp4-preempt-2.png,
> cp4-preempt-3.png, cp5-no-launch.png
>
>
> Also adds support for drawing critical path for attempts that did not get
> allocated or launched.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)