[jira] [Commented] (TEZ-4042) Speculative attempts should avoid running on the same node
[ https://issues.apache.org/jira/browse/TEZ-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772581#comment-16772581 ] Ying Han commented on TEZ-4042: --- Thanks for pointing this out, [~jeagles], this has been addressed in the new iteration of the pr. > Speculative attempts should avoid running on the same node > -- > > Key: TEZ-4042 > URL: https://issues.apache.org/jira/browse/TEZ-4042 > Project: Apache Tez > Issue Type: Bug >Reporter: Jonathan Eagles >Assignee: Ying Han >Priority: Major > Time Spent: 50m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-4042) Speculative attempts should avoid running on the same node
[ https://issues.apache.org/jira/browse/TEZ-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772376#comment-16772376 ] Jonathan Eagles commented on TEZ-4042: -- Thank you for the patch, [~Chyler]. Can we extend this to include DagAwareYarnTaskScheduler (but not LocalTaskSchedulerService)? > Speculative attempts should avoid running on the same node > -- > > Key: TEZ-4042 > URL: https://issues.apache.org/jira/browse/TEZ-4042 > Project: Apache Tez > Issue Type: Bug >Reporter: Jonathan Eagles >Assignee: Ying Han >Priority: Major > Time Spent: 40m > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (TEZ-4035) Tez master breaks with YARN 3.2.0 ApplicationReport API change
[
https://issues.apache.org/jira/browse/TEZ-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jonathan Eagles updated TEZ-4035:
-
Summary: Tez master breaks with YARN 3.2.0 ApplicationReport API change
(was: Tez master breaks with YARN 3.2.0)
> Tez master breaks with YARN 3.2.0 ApplicationReport API change
> --
>
> Key: TEZ-4035
> URL: https://issues.apache.org/jira/browse/TEZ-4035
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Rajesh Balamohan
>Assignee: Jonathan Eagles
>Priority: Minor
> Attachments: TEZ-4035.001.patch
>
>
> {noformat}
> tez/tez-mapreduce/src/main/java/org/apache/tez/mapreduce/client/NotRunningJob.java:[89,29]
> no suitable method found for
> newInstance(org.apache.hadoop.yarn.api.records.ApplicationId,org.apache.hadoop.yarn.api.records.ApplicationAttemptId,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,,org.apache.hadoop.yarn.api.records.YarnApplicationState,java.lang.String,java.lang.String,int,int,org.apache.hadoop.yarn.api.records.FinalApplicationStatus,,java.lang.String,float,java.lang.String,)
> [ERROR] method
> org.apache.hadoop.yarn.api.records.ApplicationReport.newInstance(org.apache.hadoop.yarn.api.records.ApplicationId,org.apache.hadoop.yarn.api.records.ApplicationAttemptId,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,org.apache.hadoop.yarn.api.records.Token,org.apache.hadoop.yarn.api.records.YarnApplicationState,java.lang.String,java.lang.String,long,long,long,org.apache.hadoop.yarn.api.records.FinalApplicationStatus,org.apache.hadoop.yarn.api.records.ApplicationResourceUsageReport,java.lang.String,float,java.lang.String,org.apache.hadoop.yarn.api.records.Token)
> is not applicable
> [ERROR] (actual and formal argument lists differ in length)
> [ERROR] method
> org.apache.hadoop.yarn.api.records.ApplicationReport.newInstance(org.apache.hadoop.yarn.api.records.ApplicationId,org.apache.hadoop.yarn.api.records.ApplicationAttemptId,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,org.apache.hadoop.yarn.api.records.Token,org.apache.hadoop.yarn.api.records.YarnApplicationState,java.lang.String,java.lang.String,long,long,org.apache.hadoop.yarn.api.records.FinalApplicationStatus,org.apache.hadoop.yarn.api.records.ApplicationResourceUsageReport,java.lang.String,float,java.lang.String,org.apache.hadoop.yarn.api.records.Token,java.util.Set,boolean,org.apache.hadoop.yarn.api.records.Priority,java.lang.String,java.lang.String)
> is not applicable
> [ERROR] (actual and formal argument lists differ in length)
> [ERROR] method
> org.apache.hadoop.yarn.api.records.ApplicationReport.newInstance(org.apache.hadoop.yarn.api.records.ApplicationId,org.apache.hadoop.yarn.api.records.ApplicationAttemptId,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,org.apache.hadoop.yarn.api.records.Token,org.apache.hadoop.yarn.api.records.YarnApplicationState,java.lang.String,java.lang.String,long,long,long,org.apache.hadoop.yarn.api.records.FinalApplicationStatus,org.apache.hadoop.yarn.api.records.ApplicationResourceUsageReport,java.lang.String,float,java.lang.String,org.apache.hadoop.yarn.api.records.Token,java.util.Set,boolean,org.apache.hadoop.yarn.api.records.Priority,java.lang.String,java.lang.String)
> is not applicable{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (TEZ-4042) Speculative attempts should avoid running on the same node
[ https://issues.apache.org/jira/browse/TEZ-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772082#comment-16772082 ] Harish Jaiprakash commented on TEZ-4042: Sorry, should have read better. This affects only speculative execution. Ignore comment above. > Speculative attempts should avoid running on the same node > -- > > Key: TEZ-4042 > URL: https://issues.apache.org/jira/browse/TEZ-4042 > Project: Apache Tez > Issue Type: Bug >Reporter: Jonathan Eagles >Assignee: Ying Han >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-4042) Speculative attempts should avoid running on the same node
[ https://issues.apache.org/jira/browse/TEZ-4042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16772077#comment-16772077 ] Harish Jaiprakash commented on TEZ-4042: Not sure if this is the best strategy. What happens if there is only one node or yarn keeps giving containers from one node because rest are occupied and it gets marked as unhealthy? There should be a mechanism built so that it will fall back and try on the unhealthy node. At the very least please protect it via a config. So that it can be enabled or disabled. > Speculative attempts should avoid running on the same node > -- > > Key: TEZ-4042 > URL: https://issues.apache.org/jira/browse/TEZ-4042 > Project: Apache Tez > Issue Type: Bug >Reporter: Jonathan Eagles >Assignee: Ying Han >Priority: Major > Time Spent: 0.5h > Remaining Estimate: 0h > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (TEZ-4035) Tez master breaks with YARN 3.2.0
[
https://issues.apache.org/jira/browse/TEZ-4035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16771765#comment-16771765
]
Rajesh Balamohan commented on TEZ-4035:
---
Thanks for sharing the patch [~jeagles]. Patch works fine with YARN 3.2.0.
+1
> Tez master breaks with YARN 3.2.0
> -
>
> Key: TEZ-4035
> URL: https://issues.apache.org/jira/browse/TEZ-4035
> Project: Apache Tez
> Issue Type: Bug
>Reporter: Rajesh Balamohan
>Assignee: Jonathan Eagles
>Priority: Minor
> Attachments: TEZ-4035.001.patch
>
>
> {noformat}
> tez/tez-mapreduce/src/main/java/org/apache/tez/mapreduce/client/NotRunningJob.java:[89,29]
> no suitable method found for
> newInstance(org.apache.hadoop.yarn.api.records.ApplicationId,org.apache.hadoop.yarn.api.records.ApplicationAttemptId,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,,org.apache.hadoop.yarn.api.records.YarnApplicationState,java.lang.String,java.lang.String,int,int,org.apache.hadoop.yarn.api.records.FinalApplicationStatus,,java.lang.String,float,java.lang.String,)
> [ERROR] method
> org.apache.hadoop.yarn.api.records.ApplicationReport.newInstance(org.apache.hadoop.yarn.api.records.ApplicationId,org.apache.hadoop.yarn.api.records.ApplicationAttemptId,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,org.apache.hadoop.yarn.api.records.Token,org.apache.hadoop.yarn.api.records.YarnApplicationState,java.lang.String,java.lang.String,long,long,long,org.apache.hadoop.yarn.api.records.FinalApplicationStatus,org.apache.hadoop.yarn.api.records.ApplicationResourceUsageReport,java.lang.String,float,java.lang.String,org.apache.hadoop.yarn.api.records.Token)
> is not applicable
> [ERROR] (actual and formal argument lists differ in length)
> [ERROR] method
> org.apache.hadoop.yarn.api.records.ApplicationReport.newInstance(org.apache.hadoop.yarn.api.records.ApplicationId,org.apache.hadoop.yarn.api.records.ApplicationAttemptId,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,org.apache.hadoop.yarn.api.records.Token,org.apache.hadoop.yarn.api.records.YarnApplicationState,java.lang.String,java.lang.String,long,long,org.apache.hadoop.yarn.api.records.FinalApplicationStatus,org.apache.hadoop.yarn.api.records.ApplicationResourceUsageReport,java.lang.String,float,java.lang.String,org.apache.hadoop.yarn.api.records.Token,java.util.Set,boolean,org.apache.hadoop.yarn.api.records.Priority,java.lang.String,java.lang.String)
> is not applicable
> [ERROR] (actual and formal argument lists differ in length)
> [ERROR] method
> org.apache.hadoop.yarn.api.records.ApplicationReport.newInstance(org.apache.hadoop.yarn.api.records.ApplicationId,org.apache.hadoop.yarn.api.records.ApplicationAttemptId,java.lang.String,java.lang.String,java.lang.String,java.lang.String,int,org.apache.hadoop.yarn.api.records.Token,org.apache.hadoop.yarn.api.records.YarnApplicationState,java.lang.String,java.lang.String,long,long,long,org.apache.hadoop.yarn.api.records.FinalApplicationStatus,org.apache.hadoop.yarn.api.records.ApplicationResourceUsageReport,java.lang.String,float,java.lang.String,org.apache.hadoop.yarn.api.records.Token,java.util.Set,boolean,org.apache.hadoop.yarn.api.records.Priority,java.lang.String,java.lang.String)
> is not applicable{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
