Add option, mostly for comparison's sake, that allows a deploy orchestrated by CombinedBlockCache such that its L1 is LruBlockCache for META blocks but DATA blocks are fetched each time (we don't try and cache them, no blockcache churn).
In operation, i can see fscache coming around to cover the fetched DATA blocks such that if the DATA blocks fit in fscache, seeks go to zero.
This setup for sure runs slower. Will publish numbers elsewhere. Meantime, here is a patch to enable this option.
|Status||Open [ 1 ]||Patch Available [ 10002 ]|
|Assignee||stack [ stack ]|
|Status||Patch Available [ 10002 ]||Resolved [ 5 ]|
|Release Note||Add hbase.combinedblockcache.l2.null configuration. When set to true, BlockCache uses CombinedBlockCache where L1 is instance of LruBlockCache carrying META blocks and L2 is null: i.e. DATA blocks are fetched each time.|
|Resolution||Invalid [ 6 ]|