Apache9 commented on PR #7558: URL: https://github.com/apache/hbase/pull/7558#issuecomment-3732150991
> > 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? > > We can certainly do that, but in that case I'm not sure how to generate meta table names for the replica clusters. They have to be unique at the same storage location and with files we would able to scan existing files for conflicts. By storing it in master local region I'm not sure how to do it, unless we use UUIDs as suffixes. > > Same issue arises with the directory name of Master local region of a replica cluster. Shall we use the configured replica name or the generated suffix? > > Actually this might be the right way: > > 1. Generate suffix for replica: "3a63c0f" > 2. Try to create master local region directory: "MasterData_3a63c0f" > 3. If succeeds, use this suffix for meta table name: "meta_3a63c0f" > 4. If not, go back to step 1. > > Question: how would the replica cluster know about its suffix? 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? -- 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]
