Review Board 1.7.22

[HBASE-4465] Lazy-seek optimization for StoreFile scanners

Review Request #2180 - Created Oct. 4, 2011 and updated

Mikhail Bautin
Previously, if we had several StoreFiles for a column family in a region, we would seek in each of them and only then merge the results, even though the row/column we are looking for might only be in the most recent (and the smallest) file. Now we prioritize our reads from those files so that we check the most recent file first. This is done by doing a "lazy seek" which pretends that the next value in the StoreFile is (seekRow, seekColumn, lastTimestampInStoreFile), which is earlier in the KV order than anything that might actually occur in the file. So if we don't find the result in earlier files, that fake KV will bubble up to the top of the KV heap and a real seek will be done. This is expected to significantly reduce the amount of disk IO (as of 09/22/2011 we are doing dark launch testing and measurement).

This is joint work with Liyin Tang – huge thanks to him for many helpful discussions on this and the idea of putting fake KVs with the highest timestamp of the StoreFile in the scanner priority queue.
All unit tests should be passing now. Will rebase and re-run again just in case.
Review request changed
Updated (Oct. 5, 2011, 7:11 p.m.)
Getting rid of duplicate import of AtomicLong in StoreFileScanner.
Ship it!
Posted (Oct. 5, 2011, 8:16 p.m.)