[
https://issues.apache.org/jira/browse/MAPREDUCE-4558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated MAPREDUCE-4558:
--------------------------------------
Attachment: MR4558.txt
Trivial patch - which changes the check to 3 TTs instead of 2. (Also disables
the test)
The test passes, but ends up generating cyclic attempt dir symlinks, which
cause subsequent ant operations to fail.
build/test/logs/userlogs/job_20120815112512392_0001/attempt_20120815112512392_0001_m_000000_0/attempt_20120815112512392_0001_m_000000_0/attempt_20120815112512392_0001_m_000000_0/..
The unit test was enabled as part of MAPREDUCE-3837. I'd like to disable it
again for now, with a separate jira to fix the symlinks.
> TestJobTrackerSafeMode is failing
> ---------------------------------
>
> Key: MAPREDUCE-4558
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4558
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Siddharth Seth
> Assignee: Siddharth Seth
> Attachments: MR4558.txt
>
>
> MAPREDUCE-1906 exposed an issue with this unit test. It has 3 TTs running,
> but has a check for the TT count to reach exactly 2 (which would be reached
> with a higher heartbeat interval).
> The test ends up getting stuck, with the following message repeated multiple
> times.
> {code}
> [junit] 2012-08-15 11:26:46,299 INFO mapred.TestJobTrackerSafeMode
> (TestJobTrackerSafeMode.java:checkTrackers(201)) - Waiting for Initialize all
> Task Trackers
> [junit] 2012-08-15 11:26:47,301 INFO mapred.TestJobTrackerSafeMode
> (TestJobTrackerSafeMode.java:checkTrackers(201)) - Waiting for Initialize all
> Task Trackers
> [junit] 2012-08-15 11:26:48,302 INFO mapred.TestJobTrackerSafeMode
> (TestJobTrackerSafeMode.java:checkTrackers(201)) - Waiting for Initialize all
> Task Trackers
> [junit] 2012-08-15 11:26:49,303 INFO mapred.TestJobTrackerSafeMode
> (TestJobTrackerSafeMode.java:checkTrackers(201)) - Waiting for Initialize all
> Task Trackers
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
