[jira] [Commented] (TEZ-1732) Temporary mitigation for out of order scheduling
[ https://issues.apache.org/jira/browse/TEZ-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14516324#comment-14516324 ] Bikas Saha commented on TEZ-1732: - Temporary is not relevant anymore. Temporary mitigation for out of order scheduling Key: TEZ-1732 URL: https://issues.apache.org/jira/browse/TEZ-1732 Project: Apache Tez Issue Type: Bug Reporter: Bikas Saha Assignee: Bikas Saha Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-1732) Temporary mitigation for out of order scheduling
[ https://issues.apache.org/jira/browse/TEZ-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14516261#comment-14516261 ] Hitesh Shah commented on TEZ-1732: -- [~bikassaha] [~sseth] Mind setting a target version Temporary mitigation for out of order scheduling Key: TEZ-1732 URL: https://issues.apache.org/jira/browse/TEZ-1732 Project: Apache Tez Issue Type: Bug Reporter: Bikas Saha Assignee: Bikas Saha Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-1732) Temporary mitigation for out of order scheduling
[ https://issues.apache.org/jira/browse/TEZ-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14196921#comment-14196921 ] Rajesh Balamohan commented on TEZ-1732: --- {noformat} M2 M7 M3 (sg) \ / / \/ / \ / / R3/ (b) / (sg) \ / / (b) \ / / \ / / M5 --/ | R6 {noformat} Attaching a DAG which can cause out of order execution. This happens when enough data is available to M2 and M7. Temporary mitigation for out of order scheduling Key: TEZ-1732 URL: https://issues.apache.org/jira/browse/TEZ-1732 Project: Apache Tez Issue Type: Bug Reporter: Bikas Saha Assignee: Bikas Saha Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TEZ-1732) Temporary mitigation for out of order scheduling
[ https://issues.apache.org/jira/browse/TEZ-1732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14196945#comment-14196945 ] Siddharth Seth commented on TEZ-1732: - For any vertex in the middle of a graph with a delayed CONFIGURED notification, and assuming there's no such vertices after that - the vertex with the delayed CONFIGURED and it's children will end up not scheduling tasks. Other downstream vertices will schedule their tasks. Temporary mitigation for out of order scheduling Key: TEZ-1732 URL: https://issues.apache.org/jira/browse/TEZ-1732 Project: Apache Tez Issue Type: Bug Reporter: Bikas Saha Assignee: Bikas Saha Priority: Critical -- This message was sent by Atlassian JIRA (v6.3.4#6332)