[
https://issues.apache.org/jira/browse/HBASE-29082?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17923642#comment-17923642
]
Wellington Chevreuil commented on HBASE-29082:
----------------------------------------------
{quote}[~wchevreuil] Isn't your question meant to be asked on the umbrella Jira?
I believe meta table name suffix is a pretty straightforward requirement to
avoid mixing meta information across multiple clusters on the same storage
location.
{quote}
I was just thinking about an alternative approach, where the same, single meta
table would be used by both active and read replicas, but some sort of flag
could be added to each region record to differentiate regions that should be
hosted by the active only (therefore being writable), from those hosted by read
replicas. Ain't sure if that would be easier/simpler to implement than having
multiple meta tables, just an extra idea to consider.
> Add custom meta table name suffix
> ---------------------------------
>
> Key: HBASE-29082
> URL: https://issues.apache.org/jira/browse/HBASE-29082
> Project: HBase
> Issue Type: Sub-task
> Components: master, meta
> Reporter: Andor Molnar
> Assignee: Abhishek Kothalikar
> Priority: Major
> Labels: pull-request-available
>
> Add support for custom meta table name and ability to start cluster on the
> same storage location.
> New config setting:
> |*Config*|*Default* |*Explanation*|
> |hbase.meta.table.suffix|“”|Adds a suffix to the meta table name:
> value=’test’ -> ‘hbase:meta_test’|
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
