SHARDING='NONE';为什么日志流没有在一个里面

1、在dba1手册里面,按照步骤进行操作
obclient(root@tenant1)[TEST_DB]> CREATE TABLEGROUP tbg1 SHARDING=‘NONE’;

ALTER TABLEGROUP tbg1 ADD TABLE np_t1,hp_t1;

SHOW TABLEGROUPS LIKE ‘tbg1’;Query OK, 0 rows affected (0.079 sec)

obclient(root@tenant1)[TEST_DB]> ALTER TABLEGROUP tbg1 ADD TABLE np_t1,hp_t1;

Query OK, 0 rows affected (0.094 sec)

obclient(root@tenant1)[TEST_DB]> SHOW TABLEGROUPS LIKE ‘tbg1’;

±----------------±-----------±--------------±---------+

| Tablegroup_name | Table_name | Database_name | Sharding |

±----------------±-----------±--------------±---------+

| tbg1 | hp_t1 | test_db | NONE |

| tbg1 | np_t1 | test_db | NONE |

±----------------±-----------±--------------±---------+

2 rows in set (0.012 sec)

obclient(root@tenant1)[TEST_DB]> SELECT TABLE_NAME, TABLE_ID, PARTITION_NAME, TABLET_ID, OBJECT_ID,

→ LS_ID, ZONE, SVR_IP

→ FROM oceanbase.DBA_OB_TABLE_LOCATIONS

→ WHERE DATABASE_NAME=‘TEST_DB’ AND ROLE=‘LEADER’

→ ORDER BY SVR_IP;

±-----------±---------±---------------±----------±----------±------±------±------------+

| TABLE_NAME | TABLE_ID | PARTITION_NAME | TABLET_ID | OBJECT_ID | LS_ID | ZONE | SVR_IP |

±-----------±---------±---------------±----------±----------±------±------±------------+

| hp_t1 | 500004 | p6 | 200008 | 500011 | 1001 | zone1 | 10.13.9.171 |

| hp_t1 | 500004 | p3 | 200005 | 500008 | 1001 | zone1 | 10.13.9.171 |

| hp_t1 | 500004 | p0 | 200002 | 500005 | 1001 | zone1 | 10.13.9.171 |

| hp_t1 | 500004 | p5 | 200007 | 500010 | 1003 | zone3 | 10.13.9.189 |

| hp_t1 | 500004 | p2 | 200004 | 500007 | 1003 | zone3 | 10.13.9.189 |

| np_t1 | 500003 | NULL | 200001 | 500003 | 1003 | zone3 | 10.13.9.189 |

| hp_t1 | 500004 | p7 | 200009 | 500012 | 1002 | zone2 | 10.13.9.193 |

| hp_t1 | 500004 | p4 | 200006 | 500009 | 1002 | zone2 | 10.13.9.193 |

| hp_t1 | 500004 | p1 | 200003 | 500006 | 1002 | zone2 | 10.13.9.193 |

±-----------±---------±---------------±----------±----------±------±------±------------+

9 rows in set (0.061 sec)

obclient(root@tenant1)[TEST_DB]> ALTER SYSTEM SET partition_balance_schedule_interval=‘10s’;

Query OK, 0 rows affected (0.562 sec)

obclient(root@tenant1)[TEST_DB]> SELECT TABLE_NAME, TABLE_ID, PARTITION_NAME, TABLET_ID, OBJECT_ID,

→ LS_ID, ZONE, SVR_IP

→ FROM oceanbase.DBA_OB_TABLE_LOCATIONS

→ WHERE DATABASE_NAME=‘TEST_DB’ AND ROLE=‘LEADER’

→ ORDER BY SVR_IP;

±-----------±---------±---------------±----------±----------±------±------±------------+

| TABLE_NAME | TABLE_ID | PARTITION_NAME | TABLET_ID | OBJECT_ID | LS_ID | ZONE | SVR_IP |

±-----------±---------±---------------±----------±----------±------±------±------------+

| hp_t1 | 500004 | p6 | 200008 | 500011 | 1003 | zone3 | 10.13.9.189 |

| hp_t1 | 500004 | p5 | 200007 | 500010 | 1003 | zone3 | 10.13.9.189 |

| hp_t1 | 500004 | p3 | 200005 | 500008 | 1003 | zone3 | 10.13.9.189 |

| hp_t1 | 500004 | p2 | 200004 | 500007 | 1003 | zone3 | 10.13.9.189 |

| hp_t1 | 500004 | p0 | 200002 | 500005 | 1003 | zone3 | 10.13.9.189 |

| np_t1 | 500003 | NULL | 200001 | 500003 | 1003 | zone3 | 10.13.9.189 |

| hp_t1 | 500004 | p7 | 200009 | 500012 | 1002 | zone2 | 10.13.9.193 |

| hp_t1 | 500004 | p4 | 200006 | 500009 | 1002 | zone2 | 10.13.9.193 |

| hp_t1 | 500004 | p1 | 200003 | 500006 | 1002 | zone2 | 10.13.9.193 |

±-----------±---------±---------------±----------±----------±------±------±------------+

9 rows in set (0.022 sec)

我这里的操作和实验手册里面的结果怎么不一样啊,我没到一个日志流里面

1 个赞

OB用的哪个版本呢

社区版
4.2.1.1.9

1 个赞

421bp9版本手动触发均衡任务不是partition_balance_schedule_interval参数控制了。
手动触发方式:
CALL dbms_balance.trigger_partition_balance();

表组不生效的案例文档可以参考下:
https://www.oceanbase.com/knowledge-base/oceanbase-database-1000000002830178

2 个赞

新特性现场学

学习了