Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.3.0
-
None
-
None
-
Reviewed
Description
As noted in MAPREDUCE-5584 and HADOOP-7016, LocalDirAllocator can be a bottleneck for multithreaded setups like the ShuffleHandler. We should consider moving to a lockless design or minimizing the critical sections to a very small amount of time that does not involve I/O operations.
Attachments
Attachments
Issue Links
- relates to
-
MAPREDUCE-5584 ShuffleHandler becomes unresponsive during gridmix runs and can leak file descriptors
-
- Resolved
-
-
HADOOP-7016 Optimize locking codepath in LocalDirAllocator.getLocalPathToRead() and reduce creating many Path objects
-
- Patch Available
-