社区版:版本号: 4.2.2-20240315150922
如果这个是 24 小时内的平均转储次数,这个就很不对了。 8679/24/60 ~ 6 . 意味着每分钟转储 6次。这个业务没有这么大的量。
怀疑是 BUG。
租户的24小时内 memtable 内存变化量并不是非常大,转储次数每小时平均 2次不到。
社区版:版本号: 4.2.2-20240315150922
如果这个是 24 小时内的平均转储次数,这个就很不对了。 8679/24/60 ~ 6 . 意味着每分钟转储 6次。这个业务没有这么大的量。
怀疑是 BUG。
租户的24小时内 memtable 内存变化量并不是非常大,转储次数每小时平均 2次不到。
问题已收到,稍等。
页面上展示的结果是存储在 OCP metadb 中ob_tenant_compaction 表的,由 OCP 定期采集数据,GV$OB_TABLET_COMPACTION_HISTORY 中查询出来的,可以用 sys 租户连到集群中确认一下 GV$OB_TABLET_COMPACTION_HISTORY 这个表的记录,和 OCP metadb 中 ob_tenant_compaction 的记录对比一下看看
视图 oceanbase.GV$OB_TABLET_COMPACTION_HISTORY
是按 tablet
粒度记录 compaction 记录的,这个记录数是很大的。 而租户的平均转储次数应该统计的是 租户粒度的。
当然,如果 OB 4.2 现在的转储不是租户所有分区同时触发的话,统计这个也确实有点难度。那 OCP 这个 【平均转储次数】的提示就要改改。 原本这个页面功能的目的是可以推测 租户 memtable 内存周转率。现在【转储】逻辑如果变得复杂了,这个也就不好看了。
建议让 OCP 产品经理看看这个。
MySQL [oceanbase]> SELECT svr_ip, tenant_id, ls_id,tablet_id,TYPE,start_time,finish_time FROM oceanbase.GV$OB_TABLET_COMPACTION_HISTORY WHERE tenant_id=1022 ORDER BY start_time DESC LIMIT 10;
+-------------+-----------+-------+---------------------+-------------+----------------------------+----------------------------+
| svr_ip | tenant_id | ls_id | tablet_id | TYPE | start_time | finish_time |
+-------------+-----------+-------+---------------------+-------------+----------------------------+----------------------------+
| x.x.10.38 | 1022 | 1001 | 200366 | MINOR_MERGE | 2024-05-17 09:49:17.954559 | 2024-05-17 09:49:17.968644 |
| x.x.10.38 | 1022 | 1001 | 200489 | MINOR_MERGE | 2024-05-17 09:49:17.949871 | 2024-05-17 09:49:17.950661 |
| x.x.10.38 | 1022 | 1001 | 200721 | MINOR_MERGE | 2024-05-17 09:49:17.910826 | 2024-05-17 09:49:18.033909 |
| x.x.10.38 | 1022 | 1001 | 1152921504606849457 | MINOR_MERGE | 2024-05-17 09:49:17.746507 | 2024-05-17 09:49:17.942063 |
| x.x.10.38 | 1022 | 1001 | 1152921504606849459 | MINOR_MERGE | 2024-05-17 09:49:17.733843 | 2024-05-17 09:49:18.882119 |
| x.x.10.38 | 1022 | 1001 | 200431 | MINOR_MERGE | 2024-05-17 09:49:17.729462 | 2024-05-17 09:49:17.730931 |
| x.x.10.38 | 1022 | 1001 | 1152921504606848742 | MINOR_MERGE | 2024-05-17 09:49:17.721421 | 2024-05-17 09:49:17.723401 |
| x.x.10.38 | 1022 | 1001 | 1152921504606848800 | MINOR_MERGE | 2024-05-17 09:49:17.707815 | 2024-05-17 09:49:17.716305 |
| x.x.10.38 | 1022 | 1001 | 200507 | MINOR_MERGE | 2024-05-17 09:49:17.703006 | 2024-05-17 09:49:17.704631 |
| x.x.10.38 | 1022 | 1001 | 200477 | MINOR_MERGE | 2024-05-17 09:49:17.697634 | 2024-05-17 09:49:17.699661 |
+-------------+-----------+-------+---------------------+-------------+----------------------------+----------------------------+
10 rows in set (0.42 sec)
MySQL [oceanbase]> SELECT date_format(start_time,'%Y-%m-%d') start_date, svr_ip, TYPE,count(*) cnt FROM oceanbase.GV$OB_TABLET_COMPACTION_HISTORY WHERE tenant_id=1022 GROUP BY date_format(start_time,'%Y-%m-%d'), svr_ip, TYPE WITH ROLLU
P ORDER BY 1 DESC ,2,3;
+------------+-------------+-----------------+--------+
| start_date | svr_ip | TYPE | cnt |
+------------+-------------+-----------------+--------+
| 2024-05-17 | NULL | NULL | 26483 |
| 2024-05-17 | x.x.10.36 | NULL | 8590 |
| 2024-05-17 | x.x.10.36 | MAJOR_MERGE | 2205 |
| 2024-05-17 | x.x.10.36 | MDS_TABLE_MERGE | 1622 |
| 2024-05-17 | x.x.10.36 | MEDIUM_MERGE | 72 |
| 2024-05-17 | x.x.10.36 | MINI_MERGE | 3931 |
| 2024-05-17 | x.x.10.36 | MINOR_MERGE | 760 |
| 2024-05-17 | x.x.10.37 | NULL | 8689 |
| 2024-05-17 | x.x.10.37 | MAJOR_MERGE | 2205 |
| 2024-05-17 | x.x.10.37 | MDS_TABLE_MERGE | 1617 |
| 2024-05-17 | x.x.10.37 | MEDIUM_MERGE | 72 |
| 2024-05-17 | x.x.10.37 | MINI_MERGE | 4033 |
| 2024-05-17 | x.x.10.37 | MINOR_MERGE | 762 |
| 2024-05-17 | x.x.10.38 | NULL | 9204 |
| 2024-05-17 | x.x.10.38 | MAJOR_MERGE | 2205 |
| 2024-05-17 | x.x.10.38 | MDS_TABLE_MERGE | 2215 |
| 2024-05-17 | x.x.10.38 | MEDIUM_MERGE | 72 |
| 2024-05-17 | x.x.10.38 | MINI_MERGE | 3965 |
| 2024-05-17 | x.x.10.38 | MINOR_MERGE | 747 |
.....
OCP 元数据库查询。
MySQL [meta_database]> select * from ob_tenant_compaction where tenant_id=16 order by start_time desc limit 7;
+-----+---------------------+---------------------+-----------+---------+---------------------+---------------------+---------------------+--------------------+-----------------------+-----------------+
| id | create_time | update_time | tenant_id | status | start_time | last_finish_time | frozen_scn | is_stats_collected | max_mini_freeze_count | max_mem_percent |
+-----+---------------------+---------------------+-----------+---------+---------------------+---------------------+---------------------+--------------------+-----------------------+-----------------+
| 609 | 2024-05-17 02:01:01 | 2024-05-17 02:07:01 | 16 | SUCCESS | 2024-05-17 02:00:03 | 2024-05-17 02:06:40 | 1715882402898773000 | 1 | 3647 | 73 |
| 586 | 2024-05-16 02:00:01 | 2024-05-16 02:05:00 | 16 | SUCCESS | 2024-05-16 02:00:01 | 2024-05-16 02:04:38 | 1715796000667302000 | 1 | 3600 | 76 |
| 580 | 2024-05-15 02:01:01 | 2024-05-15 02:07:01 | 16 | SUCCESS | 2024-05-15 02:00:03 | 2024-05-15 02:06:21 | 1715709603177401000 | 1 | 3553 | 73 |
| 568 | 2024-05-14 02:01:01 | 2024-05-14 02:07:01 | 16 | SUCCESS | 2024-05-14 02:00:01 | 2024-05-14 02:06:08 | 1715623200895100001 | 1 | 3505 | 76 |
| 556 | 2024-05-13 02:01:00 | 2024-05-13 02:06:01 | 16 | SUCCESS | 2024-05-13 02:00:04 | 2024-05-13 02:06:01 | 1715536803551274000 | 1 | 3458 | 74 |
| 543 | 2024-05-12 02:01:01 | 2024-05-12 02:06:01 | 16 | SUCCESS | 2024-05-12 02:00:01 | 2024-05-12 02:05:18 | 1715450401308291000 | 1 | 3410 | 73 |
| 529 | 2024-05-11 02:01:00 | 2024-05-11 02:08:00 | 16 | SUCCESS | 2024-05-11 02:00:04 | 2024-05-11 02:07:42 | 1715364004033907000 | 1 | 3362 | 75 |
+-----+---------------------+---------------------+-----------+---------+---------------------+---------------------+---------------------+--------------------+-----------------------+-----------------+
7 rows in set (0.01 sec)
租户平均转储次数在 OCP 的监控表达式上出现Bug, 预计近期发布的 OCP 4.3.0-CE会进行修复。