[
https://issues.apache.org/jira/browse/HBASE-23060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16952583#comment-16952583
]
Xiaolin Ha commented on HBASE-23060:
------------------------------------
I have a question. Why not use region name instead of row key range to manager
the infomation?
If a region has hotspot, we can move it, or move its children after splitting,
to a rsgroup? In this case, if the group region is changed, such as merged or
splitted, origin region name not exist any more, we should just adjust the
group information?
If one knows the hotspot row key range at the beginning, why he not create
another table for these keys, or why not set a region of this range to manage?
> Allow config rs group for a region
> ----------------------------------
>
> Key: HBASE-23060
> URL: https://issues.apache.org/jira/browse/HBASE-23060
> Project: HBase
> Issue Type: Sub-task
> Reporter: Duo Zhang
> Priority: Major
>
> Sometimes we only want to separate a region which is the hotspot, so it will
> be good if we can config rs group for a region.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
