Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.3.0
-
None
Description
The new disk block locations API has a configurable timeout, but it's used inconsistently: the invokeAll() call to the thread pool assumes the timeout is in seconds, but the RPC timeout is set in milliseconds.
Also, we can improve the wire protocol for this API to be a lot more efficient.
Attachments
Attachments
Issue Links
- relates to
-
HDFS-3672 Expose disk-location information for blocks to enable better scheduling
- Closed