[
https://issues.apache.org/jira/browse/HBASE-23080?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17322549#comment-17322549
]
Andrew Kyle Purtell edited comment on HBASE-23080 at 4/16/21, 1:09 AM:
-----------------------------------------------------------------------
It has to be optional. Some use cases expect strict isolation between RSGroups
and the availability tradeoff there is deliberate.
In fact, maybe it can be opt in per table, like normalization. Then the user
retains full and fine-grained control over placement policy. This can be marked
by a schema attribute in the table schema or a new field in the RSGroups table.
The latter probably makes more sense. When adding a table to a RSGroup, the add
table command can accept optional parameters. One of them would be assignment
fallback policy. We would start with two policies: default (no fallback), or
fallback (best effort). There could be more in the future. The required policy
would be exposed to the RSGroup balancer in RSGroupInfo.
was (Author: apurtell):
It has to be optional. Some use cases expect strict isolation between RSGroups
and the availability tradeoff there is deliberate.
In fact, maybe it can be opt in per table, like normalization. Then the user
retains full and fine-grained control over placement policy. This can be marked
by a schema attribute in the table schema or a new field in the RSGroups table.
The latter probably makes more sense. When adding a table to a RSGroup, the add
table command can accept optional parameters. One of them would be assignment
fallback policy. We would start with two policies: default (no fallback), or
fallback (best effort). There could be more in the future.
> Purge LoadBalancer.BOGUS_SERVER_NAME in rsgroup
> -----------------------------------------------
>
> Key: HBASE-23080
> URL: https://issues.apache.org/jira/browse/HBASE-23080
> Project: HBase
> Issue Type: Improvement
> Components: rsgroup
> Reporter: Xiaolin Ha
> Assignee: Xiaolin Ha
> Priority: Minor
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
