You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "chenxu (JIRA)" <ji...@apache.org> on 2018/06/21 09:20:00 UTC
[jira] [Updated] (HBASE-20768) should we bypass the
RegionLocationFinder#scheduleFullRefresh execution when master has not
initialized
[ https://issues.apache.org/jira/browse/HBASE-20768?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
chenxu updated HBASE-20768:
---------------------------
Attachment: HBASE-20768-master-v1.patch
> should we bypass the RegionLocationFinder#scheduleFullRefresh execution when master has not initialized
> -------------------------------------------------------------------------------------------------------
>
> Key: HBASE-20768
> URL: https://issues.apache.org/jira/browse/HBASE-20768
> Project: HBase
> Issue Type: Improvement
> Components: Balancer
> Reporter: chenxu
> Priority: Major
> Attachments: HBASE-20768-master-v1.patch
>
>
> Our KYLIN cluster has about 300K Regions, when master startup, It takes a long time to do RegionLocationFinder#scheduleFullRefresh.
> During this period, CUBE cannot be built, because master has not initialized.
> Although we can ignore locality factor through HBASE-18478, but i think it would be better if we bypass the RegionLocationFinder#scheduleFullRefresh until the master initialized
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)