[
https://issues.apache.org/jira/browse/MAPREDUCE-5481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13772495#comment-13772495
]
Xuan Gong commented on MAPREDUCE-5481:
--------------------------------------
[~jlowe][~masokan] I did the localtest, too. Looks like the client can connect
to RM. NM do the heartbeat normally, container status looks fine. But after
mapper tasks finish, the reducer task will never start. The more weird thing is
that (the reducer task will never start) happens when we set number of reducer
is 1, but if i increase the number of reducer to 2, the reducers can start to
work...
I double checked the 2.1.beta, this test works, but it can not work on trunk. I
am wondering if we made some changes after 2.1.beta to fail this test.
Any idea ?
> TestUberAM timeout
> ------------------
>
> Key: MAPREDUCE-5481
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5481
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: mrv2, test
> Affects Versions: 3.0.0
> Reporter: Jason Lowe
> Assignee: Xuan Gong
> Priority: Blocker
>
> TestUberAM has been timing out on trunk for some time now and surefire then
> fails the build. I'm not able to reproduce it locally, but the Jenkins
> builds have been seeing it fairly consistently. See
> https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1529/console
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
