GCDW垃圾回收功能说明

1.垃圾回收参数说明：
gcdw_garbage_collect_interval_seconds：检查参数，多长时间检查是否存在可回收的旧版文件（pcfile与pfile）
gcdw_garbage_clear_interval_seconds：清理参数，多长时间将检查到可回收的文件进行清理
gcdw_garbage_ergodic_s3_interval_seconds：检查参数，多长时间检查s3中残留的垃圾文件（服务异常产生的文件，pfile中不存在的）

2.pfile与pcfile对应关系查看方法：
select * from performance_schema.PFILE_INFO where pfkey =‘instance:gcdw:dbs:dbid:8:tbid:9:datameta:pid:14592:wid:32:rid:31’;

pfkey查看方法，需要在fdb客户端执行：
查看库信息：
fdb> getrange instance:test:dbs:dbids: instance:test:dbs:dbids:z
Range limited to 25 keys
instance:test:dbs:dbids:31' is \x08vc00001_lydb’
instance:test:dbs:dbids:6' is \x08vc00001_gclusterdb’
其中test为s3中的桶名，查询结果中的lydb为要查询的数据库名，找到其对应的dbid：31

查看表信息：
fdb> getrange instance:test:dbs:dbid:31:tbids: instance:test:dbs:dbid:31:tbids:z
Range limited to 25 keysinstance:test:dbs:dbid:31:tbids:50' is \x08t1’

根据得到的库信息31,查询得到lydb库下的表信息，找到对应的tbids：50

查看表的版本号： pid相同wid不同的为不同的版本文件
fdb> getrangekeys instance:test:dbs:dbid:31:tbid:50:datameta:a instance:test:dbs:dbid:31:tbid:50:datameta:z
Range limited to 25
keysinstance:test:dbs:dbid:31:tbid:50:datameta:pid:16776960:wid:779:rid:0' instance:test:dbs:dbid:31:tbid:50:datameta:pid:33554176:wid:785:rid:784’

根据查询得到的instance可获得详细信息
gbase> select json from performance_schema.PFILE_INFO where pfkey =‘instance:test:dbs:dbid:31:tbid:50:datameta:pid:33554176:wid:779:rid:0’ \G

3.根据上述过程到照pf与pcf的对应关系，在浏览器中打开http://10.10.4.70:9000/minio/liuyang/instance/test/dbs/dbid/31/tbid/50/data/pid/观察pcf的各个版本
其中31为库id，50为表id

4.查看垃圾回收日志
首先将express.log的日志等级设为7
gbase> show variables like ‘%log_level%’;
±-----------------------±------+
| Variable_name | Value |
±-----------------------±------+
| _gbase_inmem_log_level | 1 |
| gbase_log_level | 3 |
| gcluster_log_level | 7 |
±-----------------------±------+

通过查询关键字Garbage可找到垃圾回收对应的信息
[gbase@liuyang-node-0 gcluster]$ tail -f express.log
2022-09-19 11:05:51.704 GCDW GARBAGE INFO<DoGarbageErgodicCollectPF|2034>:Garbage egrodic, Start Get all PaxFile
2022-09-19 11:05:51.704 GCDW GARBAGE INFO<DoGarbageErgodicCollectPF|2034>:Garbage egrodic, Start Get all PaxFile
2022-09-19 11:06:01.733 GCDW GARBAGE INFO<DoGarbageErgodic|2022>:Start garbage egrodic, prepare for clear it. TXID:2191
2022-09-19 11:06:01.740 [GARBAGE_MGR][INFO ]:Begin to m_pThreadPool->AssignWork(). Create 2 threads.
2022-09-19 11:06:01.740 GCDW GARBAGE INFO<DoGarbageErgodicCollectPF|2034>:Garbage egrodic, Start Get all PaxFile
2022-09-19 11:06:01.740 GCDW GARBAGE INFO<DoGarbageErgodicCollectPF|2034>:Garbage egrodic, Start Get all PaxFile
2022-09-19 11:06:11.770 GCDW GARBAGE INFO<DoGarbageErgodic|2022>:Start garbage egrodic, prepare for clear it. TXID:2191
2022-09-19 11:06:11.778 [GARBAGE_MGR][INFO ]:Begin to m_pThreadPool->AssignWork(). Create 2 threads.
2022-09-19 11:06:11.779 GCDW GARBAGE INFO<DoGarbageErgodicCollectPF|2034>:Garbage egrodic, Start Get all PaxFile
2022-09-19 11:06:11.779 GCDW GARBAGE INFO<DoGarbageErgodicCollectPF|2034>:Garbage egrodic, Start Get all PaxFile
2022-09-19 11:06:21.811 GCDW GARBAGE INFO<DoGarbageErgodic|2022>:Start garbage egrodic, prepare for clear it. TXID:2191
2022-09-19 11:06:21.819 [GARBAGE_MGR][INFO ]:Begin to m_pThreadPool->AssignWork(). Create 2 threads.
2022-09-19 11:06:21.820 GCDW GARBAGE INFO<DoGarbageErgodicCollectPF|2034>:Garbage egrodic, Start Get all PaxFile
2022-09-19 11:06:21.820 GCDW GARBAGE INFO<DoGarbageErgodicCollectPF|2034>:Garbage egrodic, Start Get all PaxFile

5.在web查看文件，通过查看库信息与表信息找到对应目录，目录下存在pfile文件