[ https://issues.apache.org/jira/browse/HBASE-2468?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870331#action_12870331 ]
stack commented on HBASE-2468: ------------------------------ Hmm... if you can't scan the whole table, then this patch gets more complicated I believe. You'll need to prefix the scan with a getClosestsRowBefore to find where to start the short scan of the next N items. Also, the way that rowUpperLimit works in this patch seems like it might be broke. We'll only ever get the first rowUpperLimit items in the table... is that right? > Improvements to prewarm META cache on clients > --------------------------------------------- > > Key: HBASE-2468 > URL: https://issues.apache.org/jira/browse/HBASE-2468 > Project: Hadoop HBase > Issue Type: Improvement > Components: client > Reporter: Todd Lipcon > Assignee: Mingjie Lai > Fix For: 0.21.0 > > Attachments: HBASE-2468-trunk.patch > > > A couple different use cases cause storms of reads to META during startup. > For example, a large MR job will cause each map task to hit meta since it > starts with an empty cache. > A couple possible improvements have been proposed: > - MR jobs could ship a copy of META for the table in the DistributedCache > - Clients could prewarm cache by doing a large scan of all the meta for the > table instead of random reads for each miss > - Each miss could fetch ahead some number of rows in META -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.