[
https://issues.apache.org/jira/browse/HBASE-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13019223#comment-13019223
]
Nicolas Spiegelberg commented on HBASE-3763:
--------------------------------------------
@stack: we ran into a problem where our bloom sizes were getting quite
substantial (100 MB. Believe it or not, blooms still make sense here). When
this is not in the LRU cache, read requests stall until the entire bloom is
loaded into memory. Sometimes, this can be a non-local read. If we can do a
block index for blooms and only have to load a 64kb shard, our read stalls will
severely diminish.
> Add Bloom Block Index Support
> -----------------------------
>
> Key: HBASE-3763
> URL: https://issues.apache.org/jira/browse/HBASE-3763
> Project: HBase
> Issue Type: Improvement
> Components: io, regionserver
> Affects Versions: 0.89.20100924, 0.90.0, 0.90.1, 0.90.2
> Reporter: mikhail
> Assignee: mikhail
> Priority: Minor
> Labels: hbase, performance
> Fix For: 0.89.20100924
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> Add a way to save HBase Bloom filters into an array of Meta blocks instead of
> one big Meta block, and load only the blocks required to answer a query.
> This will allow us faster bloom load times for large StoreFiles & pave the
> path for adding Bloom Filter support to HFileOutputFormat bulk load.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
