Our database cluster has 3 zones. We first create a new tenant with only 2 zones, and then create a new table.
When changing the tenant attribute from 2 zones to 3 zones, there are still 2 zones in the table. Is this correct? How to change the table to 3 copies too?
I tried modifying the tenant's resource_pool_list, but it doesn't work. Is modifying locality the right way?
Environment
- database version:
Server version: 5.7.25 OceanBase_CE 4.0.0.0
- Hardware parameter:
OS: Ubuntu 18.04; CPU: Intel(R) Xeon(R) Gold 6230R CPU @ 2.10GHz
How do I solve this, would really appreciate if someone have any leads.
CodePudding user response:
adding zone to the tenant attribute will not change the table, you need to supplement the copy manually. "resource_pool_list" is a list of resource pools, and "locality" is used to set copy attributes.