You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Vladimir Rodionov (JIRA)" <ji...@apache.org> on 2015/10/21 21:50:27 UTC
[jira] [Updated] (HBASE-14663) HStore::close does not honor config
hbase.rs.evictblocksonclose
[ https://issues.apache.org/jira/browse/HBASE-14663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Vladimir Rodionov updated HBASE-14663:
--------------------------------------
Attachment: HBASE-14663-v1.patch
> HStore::close does not honor config hbase.rs.evictblocksonclose
> ---------------------------------------------------------------
>
> Key: HBASE-14663
> URL: https://issues.apache.org/jira/browse/HBASE-14663
> Project: HBase
> Issue Type: Bug
> Components: BlockCache, regionserver
> Affects Versions: 1.0.0
> Reporter: Randy Fox
> Assignee: Vladimir Rodionov
> Priority: Minor
> Attachments: HBASE-14663-v1.patch
>
>
> I noticed moving regions was slow and due to the wait for the bucket cache to clear. I tried setting hbase.rs.evictblocksonclose and it did not help.
> I see the HStore::close method has evictonclose hard coded to true instead of letting the config dictate:
> // close each store file in parallel
> CompletionService<Void> completionService =
> new ExecutorCompletionService<Void>(storeFileCloserThreadPool);
> for (final StoreFile f : result) {
> completionService.submit(new Callable<Void>() {
> @Override
> public Void call() throws IOException {
> f.closeReader(true);
> return null;
> }
> });
> }
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)