[ https://issues.apache.org/jira/browse/HBASE-25278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17231057#comment-17231057 ]
Zach York commented on HBASE-25278: ----------------------------------- Looks like an easy way to enable this use case. +1 Longer term, I wonder if it makes sense to add a warmup/cache blocks top level utility in hbase admin/shell since a user really shouldn't need to have to actually return any data if all they care about is warming the cache. This might give a better user experience for people who don't want to pay the region open penalty for prefetch on open, but still want to avoid a cold cache. > Add option to toggle CACHE_BLOCKS in count.rb > --------------------------------------------- > > Key: HBASE-25278 > URL: https://issues.apache.org/jira/browse/HBASE-25278 > Project: HBase > Issue Type: New Feature > Components: shell > Reporter: Josh Elser > Assignee: Josh Elser > Priority: Minor > Fix For: 3.0.0-alpha-1, 2.4.0 > > > A trick I've found myself doing a couple of times (hat-tip to [~psomogyi]) is > to edit table.rb so that the `count` shell command will not instruct > RegionServers to not cache any data blocks. This is a quick+dirty way to > force a table to be loaded into block cache (i.e. for performance testing). > We can easily add another option to avoid having to edit the ruby files. -- This message was sent by Atlassian Jira (v8.3.4#803005)