Apache9 commented on PR #7558: URL: https://github.com/apache/hbase/pull/7558#issuecomment-3677639679
> > > > Let's not introduce new persistent data on zookeeper, we could store it on HDFS on in the master local region. Maybe we should introduce a shell command like 'add_read_replica_cluster xxx' and execute it at the primary cluster, the primary cluster will generate the meta name suffix file or record for read replica clusters. > > > > > > > > > HDFS won't be sufficient, because it's shared between the clusters. Could be in master local region, but that doesn't contradict with making it accessible via `ConnectionRegistry`. Is that correct? > > > > > > We coud use different file names for different read replica clusters? > > So basically, we read from the config: > > ``` > <property> > <name>hbase.read.replica.id</name> > <value>replica1</value> > </property> > ``` > > and create a file on HDFS: `hbase.replica1` > > ``` > meta_table_name=hbase:meta_3a63c0f > ``` > > ? Was thinking of this approach. But after considering, if we could use different master local region for different HBase read replicas, we could just store this value in master local region? In this way the primary cluster does not need to know the read replicas. Maybe this is better? -- 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]
