hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Lowe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-7064) Flaky test TestTaskAttempt#testReducerCustomResourceTypes
Date Tue, 13 Mar 2018 16:06:00 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-7064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16397175#comment-16397175

Jason Lowe commented on MAPREDUCE-7064:

Thanks for the patch!  Looks like a reasonable approach to me.  Curious, why the isInState(STATE.STOPPED)
check before calling close but only in one instance?  Looks like the close method already
does nothing if it is in the stopped state, so this looks like extraneous code.

> Flaky test TestTaskAttempt#testReducerCustomResourceTypes
> ---------------------------------------------------------
>                 Key: MAPREDUCE-7064
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7064
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: client, test
>            Reporter: Peter Bacsko
>            Assignee: Peter Bacsko
>            Priority: Major
>         Attachments: MAPREDUCE-7064-001.patch
> The test {{TestTaskAttempt#testReducerCustomResourceType}} can occasionally fail with
the following error:
> {noformat}
> org.apache.hadoop.yarn.exceptions.ResourceNotFoundException: Unknown resource 'a-custom-resource'.
Known resources are [name: memory-mb, units: Mi, type: COUNTABLE, value: 0, minimum allocation:
0, maximum allocation: 9223372036854775807, name: vcores, units: , type: COUNTABLE, value:
0, minimum allocation: 0, maximum allocation: 9223372036854775807]
> 	at org.apache.hadoop.mapreduce.v2.app.job.impl.TestTaskAttempt.createReduceTaskAttemptImplForTest(TestTaskAttempt.java:434)
> 	at org.apache.hadoop.mapreduce.v2.app.job.impl.TestTaskAttempt.testReducerCustomResourceTypes(TestTaskAttempt.java:1535)
> {noformat}
> The root cause seems to be an interference from previous tests that start instance(s)
of {{FailingAttemptsMRApp}} or {{FailingAttemptsDuringAssignedMRApp}}. When I disabled these
tests, {{testReducerCustomResourceTypes}} always passed.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org

View raw message