[
https://issues.apache.org/jira/browse/HBASE-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12671658#action_12671658
]
Jean-Daniel Cryans commented on HBASE-1187:
-------------------------------------------
I think it could be an issue for tables that stay small under particular
situations. If hbase.regions.percheckin was configurable, it would solve our
problem. RegionManager is even ready for this.
{code}
this.maxAssignInOneGo = conf.getInt("hbase.regions.percheckin", 10);
{code}
I will just add it to hbase-default.xml and close this case. Thank you for the
pointer Stack!
> After disabling/enabling a table, the regions seems to be assigned to only
> 1-2 region servers
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-1187
> URL: https://issues.apache.org/jira/browse/HBASE-1187
> Project: Hadoop HBase
> Issue Type: Bug
> Components: master
> Affects Versions: 0.19.0
> Reporter: Jean-Daniel Cryans
>
> After disabling/enabling a small table (20 regions), we see that the master
> tend to assign the regions to only 1-2 region servers. Unfortunately, that
> table is extensively used in random reads which really kills those RS when
> they hold those regions. As a fix, we have to restart HBase...
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
