Apache9 commented on PR #7558: URL: https://github.com/apache/hbase/pull/7558#issuecomment-3744944062
> > Anyway you need something in the configuration to tell a cluster that you are a read replica cluster or not, so you can just add a configuration named replica_suffix? > > That's where we started. It's already there: > > ``` > <property> > <name>hbase.read.replica.id</name> > <value>replica1</value> > </property> > ``` > > I think we started the conversation about whether we should use this replica.id in the meta table and master region directory name or generate a random value for each replica? As long as the replica id must be unique, I think use it as master local region's suffix is enough? For meta table, I'm nature on whether to reuse this id too, or we could generate one and store it in master local region, seems the former one is enough but the latter is more flexible, and as said above, theoretically we could even change the meta table name. Thanks. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
