[HADOOP-14535] wasb: implement high-performance random access and seek of block blobs

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.9.0, 3.0.0-beta1
• Component/s: fs/azure
• Target Version/s: 2.9.0, 3.0.0-beta1
• Release Note: Random access and seek improvements for the wasb:// (Azure) file system.
• Flags: Patch
• Assignee: Thomas Marqardt
• Reporter: Thomas Marqardt
• Created: 17/Jun/17 00:09
• Updated: 08/Aug/17 13:49
• Resolved: 11/Jul/17 20:45

Description

This change adds a seek-able stream for reading block blobs to the wasb:// file system.

If seek() is not used or if only forward seek() is used, the behavior of read() is unchanged.
That is, the stream is optimized for sequential reads by reading chunks (over the network) in
the size specified by "fs.azure.read.request.size" (default is 4 megabytes).

If reverse seek() is used, the behavior of read() changes in favor of reading the actual number
of bytes requested in the call to read(), with some constraints. If the size requested is smaller
than 16 kilobytes and cannot be satisfied by the internal buffer, the network read will be 16
kilobytes. If the size requested is greater than 4 megabytes, it will be satisfied by sequential
4 megabyte reads over the network.

This change improves the performance of FSInputStream.seek() by not closing and re-opening the
stream, which for block blobs also involves a network operation to read the blob metadata. Now
NativeAzureFsInputStream.seek() checks if the stream is seek-able and moves the read position.

[^attachment-name.zip]

Issue Links

• depends upon: HADOOP-14722 Azure: BlockBlobInputStream position incorrect after seek
• depends upon: HADOOP-14680 Azure: IndexOutOfBoundsException in BlockBlobInputStream
• is depended upon by: HADOOP-14552 Über-jira: WASB client phase II: performance and testing