[
https://issues.apache.org/jira/browse/MAPREDUCE-1366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Douglas updated MAPREDUCE-1366:
-------------------------------------
Status: Open (was: Patch Available)
Failures appear related to MAPREDUCE-1275. Will try again.
bq. When i tried to test the patch, I realized that the test timeout on
MAPREDUCE-1365 is because of MAPREDUCE-1371.
*nod* Yes, you're right. I hadn't tested that. The test timeout wasn't my
motivation, but the spurious failure in MAPREDUCE-64 that would be easier to
diagnose.
bq. I would only set the fatalError value if it is not null, so that the
earliest fault gets retained. A setFatalError() method could do this.
I don't see what you mean. Each tracker retains its cause of death; it's not
shared between them and each tracker should only set this once. Are you
suggesting making the error global and retaining only the first fault across
all trackers?
bq. Also, this may be an opportunity to give the MiniMRCluster and MinDFS
cluster a common base class rather than continue to duplicate code.
Refactoring the Mini\*Clusters is out of scope for this issue. This is just
making the cause of test failures related to HADOOP-4744 clearer.
> Tests should not timeout if TaskTracker/JobTracker crashes in MiniMRCluster
> ---------------------------------------------------------------------------
>
> Key: MAPREDUCE-1366
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1366
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: test
> Reporter: Amareshwari Sriramadasu
> Fix For: 0.22.0
>
> Attachments: M1366-0.patch
>
>
> Currently tests timeout if there is any problem bringing up JobTracker or
> TaskTracker in MiniMRCluster. Instead tests should fail saying JT/TT crashed.
> See test timeout on MAPREDUCE-1365
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
