Details
-
Task
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
Reviewed
Description
In the current implementation, Fetcher instances usually exit gracefully when the shuffle succeeds. When it fails, threads are interrupted, but may continue running harmlessly until the JVM shuts down.
However, to generate consistent checkpoints, these threads should exit cleanly to quiesce the state of the shuffle.
Attachments
Attachments
Issue Links
- breaks
-
MAPREDUCE-5456 TestFetcher.testCopyFromHostExtraBytes is missing
- Closed
- is part of
-
MAPREDUCE-4584 Umbrella: Preemption and restart of MapReduce tasks
- Open