Note
This parameter is no longer applicable after V4.0.0, when the architecture was upgraded.
Description
ilog_index_expire_time specifies the maximum time for which an OBServer node can provide Ilog files.
Attributes
| Attribute | Description |
|---|---|
| Type | Time type |
| Default value | 60d, which indicates 60 days |
| Value range | [0s,120d) |
| Effective upon OBServer node restart | No |
Considerations
In OceanBase Database, the file_id_cache cache stores the metadata information of all Ilog files, and records the starting log number and timestamp of each partition in these Ilog files. By default, the cache is cleared only when an Ilog file is deleted. Therefore, on machines with large disk space, the file_id_cache cache may occupy a large amount of memory. This situation is further exacerbated when partitions are frequently created and deleted.
You can adjust the value of the ilog_index_expire_time parameter to reduce the memory usage of the file_id_cache cache. The ilog_index_expire_time parameter specifies the maximum time for which an OBServer node can provide Ilog files. Ilog files that exceed this time limit will not be cached in the file_id_cache cache, thereby reducing memory usage.
When you set the value of this parameter:
If you shorten the time limit, the system will quickly clear the memory usage of the
file_id_cachecache. After the setting is applied, you can query the memory usage of theob_csr_file_id_cachecache to observe the effect.If you extend the time limit, the system will cache Ilog files with a larger time span after the machine is restarted.
Examples
obclient> ALTER SYSTEM SET ilog_index_expire_time = '7d';