[
https://issues.apache.org/jira/browse/TEZ-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522650#comment-16522650
]
Gopal V commented on TEZ-3958:
------------------------------
[~jmarhuen]: yes, you are right - however the priority limits for the task
itself is computed within the scheduler here.
https://github.com/apache/tez/blob/3f2373e2b2ab3825ef50e9f19b8704265542a8b2/tez-dag/src/main/java/org/apache/tez/dag/app/dag/impl/DAGSchedulerNaturalOrder.java#L47
{code}
int priorityLowLimit = ((vertexDistanceFromRoot + 1) * dag.getTotalVertices() *
3) + (vertex.getVertexId().getId() * 3);
{code}
> Add internal vertex priority information into the tez dag.dot debug
> information
> -------------------------------------------------------------------------------
>
> Key: TEZ-3958
> URL: https://issues.apache.org/jira/browse/TEZ-3958
> Project: Apache Tez
> Issue Type: Improvement
> Reporter: Gopal V
> Priority: Major
>
> Adding the actual vertex priority as computed by Tez into the debug dag.dot
> file would allows the debugging of task pre-emption issues when the DAG is no
> longer a tree.
> There are pre-emption issues with isomerization of Tez DAGs, where the a
> R-isomer dag with mirror rotation runs at a different speed than the L-isomer
> dag, due to priorities at the same level changing due to the vertex-id order.
> Since the problem is hard to debug through, it would be good to record the
> computed priority in the DAG .dot file in the logging directories.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
