[jira] [Updated] (TEZ-3958) Add internal vertex priority information into the tez dag.dot debug information
[ https://issues.apache.org/jira/browse/TEZ-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaume M updated TEZ-3958: - Attachment: TEZ-3958.1.patch > 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 > Attachments: TEZ-3958.1.patch > > > 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)
[jira] [Updated] (TEZ-3958) Add internal vertex priority information into the tez dag.dot debug information
[ https://issues.apache.org/jira/browse/TEZ-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jaume M updated TEZ-3958: - Attachment: (was: TEZ-3958.3.patch) > 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 >Assignee: Jaume M >Priority: Major > Attachments: TEZ-3958.1.patch, TEZ-3958.2.patch, TEZ-3958.3.patch > > > 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)
[jira] [Updated] (TEZ-3958) Add internal vertex priority information into the tez dag.dot debug information
[ https://issues.apache.org/jira/browse/TEZ-3958?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gopal V updated TEZ-3958: - Attachment: TEZ-3958.5.patch > 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 >Assignee: Gopal V >Priority: Major > Attachments: TEZ-3958.1.patch, TEZ-3958.2.patch, TEZ-3958.3.patch, > TEZ-3958.4.patch, TEZ-3958.5.patch > > > 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)
