你去回答问题 赚的积分 或者看看实名什么信息的填写一下 应该就可以发附件了
你把资源池给删除 你用这样的方式 kubectl apply -f tenant.yaml 创建以后 看看是否有问题 看着ob-operator操作 都是通过这样的方式操作
https://www.oceanbase.com/docs/community-ob-operator-doc-1000000003098086
好的，我试一下
结果还是分布在zone1的一个observer
mysql> SELECT count(*) FROM oceanbase.CDB_OB_TABLE_LOCATIONS WHERE DATABASE_NAME = 'test' and role = 'leader' and svr_ip = '10.244.214.107';
+----------+
| count(*) |
+----------+
| 4000 |
+----------+
1 row in set (0.17 sec)
mysql> SELECT count(*) FROM oceanbase.CDB_OB_TABLE_LOCATIONS WHERE DATABASE_NAME = 'test' and role = 'leader' and svr_ip != '10.244.214.107';
+----------+
| count(*) |
+----------+
| 0 |
+----------+
1 row in set (0.16 sec)
mysql> SELECT TENANT_ID,TENANT_NAME,TENANT_TYPE,PRIMARY_ZONE,LOCALITY FROM oceanbase.DBA_OB_TENANTS;
+-----------+---------------+-------------+-------------------+---------------------------------------------+
| TENANT_ID | TENANT_NAME | TENANT_TYPE | PRIMARY_ZONE | LOCALITY |
+-----------+---------------+-------------+-------------------+---------------------------------------------+
| 1 | sys | SYS | RANDOM | FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3 |
| 1009 | META$1010 | META | zone1;zone2;zone3 | FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3 |
| 1010 | tenant_test_0 | USER | zone1;zone2;zone3 | FULL{1}@zone1, FULL{1}@zone2, FULL{1}@zone3 |
+-----------+---------------+-------------+-------------------+---------------------------------------------+
3 rows in set (0.02 sec)
mysql> select TENANT_ID,LS_ID,STATUS,PRIMARY_ZONE,UNIT_GROUP_ID,LS_GROUP_ID from oceanbase.CDB_OB_LS;
+-----------+-------+--------+-------------------+---------------+-------------+
| TENANT_ID | LS_ID | STATUS | PRIMARY_ZONE | UNIT_GROUP_ID | LS_GROUP_ID |
+-----------+-------+--------+-------------------+---------------+-------------+
| 1 | 1 | NORMAL | zone1,zone2,zone3 | 0 | 0 |
| 1009 | 1 | NORMAL | zone1;zone2;zone3 | 0 | 0 |
| 1010 | 1 | NORMAL | zone1;zone2;zone3 | 0 | 0 |
| 1010 | 1001 | NORMAL | zone1;zone2;zone3 | 1008 | 1001 |
| 1010 | 1002 | NORMAL | zone1;zone2;zone3 | 1009 | 1002 |
| 1010 | 1003 | NORMAL | zone1;zone2;zone3 | 0 | 0 |
+-----------+-------+--------+-------------------+---------------+-------------+
6 rows in set (0.03 sec)
mysql> select UNIT_ID,TENANT_ID,UNIT_GROUP_ID,ZONE,SVR_IP,SVR_PORT from oceanbase.DBA_OB_UNITS;
+---------+-----------+---------------+-------+----------------+----------+
| UNIT_ID | TENANT_ID | UNIT_GROUP_ID | ZONE | SVR_IP | SVR_PORT |
+---------+-----------+---------------+-------+----------------+----------+
| 1 | 1 | 1 | zone1 | 10.244.136.35 | 2882 |
| 2 | 1 | 1 | zone2 | 10.244.163.98 | 2882 |
| 3 | 1 | 1 | zone3 | 10.244.214.92 | 2882 |
| 1025 | 1010 | 1008 | zone1 | 10.244.214.107 | 2882 |
| 1026 | 1010 | 1009 | zone1 | 10.244.136.35 | 2882 |
| 1027 | 1010 | 1008 | zone2 | 10.244.136.32 | 2882 |
| 1028 | 1010 | 1009 | zone2 | 10.244.163.98 | 2882 |
| 1029 | 1010 | 1008 | zone3 | 10.244.163.120 | 2882 |
| 1030 | 1010 | 1009 | zone3 | 10.244.214.92 | 2882 |
+---------+-----------+---------------+-------+----------------+----------+
9 rows in set (0.00 sec)
tenant.yaml
apiVersion: oceanbase.oceanbase.com/v1alpha1
kind: OBTenant
metadata:
name: tenant-test-0
namespace: oceanbase
spec:
obcluster: vsmongo
tenantName: tenant_test_0
unitNum: 2
charset: utf8mb4
connectWhiteList: '%'
forceDelete: true
credentials:
root: root-password
# standbyRo: t1-ro
pools:
- zone: zone1
type:
name: Full
replica: 1
isActive: true
priority: 3
resource:
maxCPU: 13
minCPU: 13
memorySize: 24Gi
maxIops: 9223372036
minIops: 9223372036
iopsWeight: 2
logDiskSize: 72Gi
- zone: zone2
type:
name: Full
replica: 1
isActive: true
priority: 2
resource:
maxCPU: 13
minCPU: 13
memorySize: 24Gi
maxIops: 9223372036
minIops: 9223372036
iopsWeight: 2
logDiskSize: 72Gi
- zone: zone3
type:
name: Full
replica: 1
isActive: true
priority: 1
resource:
maxCPU: 13
minCPU: 13
memorySize: 24Gi
maxIops: 9223372036
minIops: 9223372036
iopsWeight: 2
logDiskSize: 72Gi
上次的日志信息 你尽量提供一下
日志信息已提供，请查看
这个日志 是你删除和增加资源池的时间段日志么？看着日志时间不对呀 你看看observer.log的归档日志
这个日志是我让他帮我上传的。下午2:30直接从pod里面拷贝出来的，不包含后面使用 tenant.yaml 去创建租户的日志
看着日志时间不对呀 你看看observer.log的归档日志 归档日志类似这样的 在同一个目录
我只拷贝了这两个文件
应该是日志归档了 你在看看对应时间段的日志 麻烦在拷贝一下
日志超过100MB没法上传，我弄到百度网盘了(回复也限制了，要不再开一个帖子吧)：
通过网盘分享的文件：log.zip
链接: https://pan.baidu.com/s/1jR72vIFutikL7E16w6egIA?pwd=hvmr 提取码: hvmr
我在 2025-08-28 18:39:07 重试了一遍 apply -f tenant.yaml，然后创建分区表
我们没有办法 从网盘下载 能分开发么
可以的，你发个新帖吧，日志可以分批上传，压缩下，一次上限是50M
创建的表是复制表，当创建一个复制表后，所在租户的所有observer内都会创建一个复制表的副本，这些副本中有一个副本会被选为Leader，接受写请求，其余的副本只能接受读请求。复制表是广播日志流，对应的unit_group_id=0。