[
https://issues.apache.org/jira/browse/MAPREDUCE-7280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17148258#comment-17148258
]
Hudson commented on MAPREDUCE-7280:
-----------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #18390 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/18390/])
MAPREDUCE-7280. MiniMRYarnCluster has hard-coded timeout waiting to (github:
rev 7e73cad97419671b1020906bef36ad60aaa70ab9)
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapreduce/v2/MiniMRYarnCluster.java
* (edit)
hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-jobclient/src/test/java/org/apache/hadoop/mapred/TestMiniMRBringup.java
> MiniMRYarnCluster has hard-coded timeout waiting to start history server,
> with no way to disable
> ------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-7280
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-7280
> Project: Hadoop Map/Reduce
> Issue Type: Test
> Components: test
> Reporter: Nick Dimiduk
> Assignee: Masatake Iwasaki
> Priority: Major
> Fix For: 3.4.0
>
>
> Over in HBase, we've been chasing intermittent Jenkins failures in tests
> involving MiniMRYarnCluster. In the latest incantion, HBASE-24493, we
> finally tracked this down to a hard-coded 60sec timeout in MiniMRYarnCluster
> on bringing up the JobHistoryServer... a feature we cannot disable for the
> purpose of this test. We've had to disable running these tests for the time
> being, which is less than ideal.
> Would be great for MiniMRYarnCluster to (1) make JHS optional and/or (2) make
> this timeout duration configurable.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
