Issues Regarding TiKV TTL

Note:
This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 关于TiKV TTL的问题

| username: 我家有个臭皮崽

I see that there is a TTL setting in the PB file for interacting with TiKV, which seems to allow setting TTL time for each key individually:

message RawCASRequest {
    Context context = 1;
    bytes key = 2;
    bytes value = 3;
    bool previous_not_exist = 4;
    bytes previous_value = 5;
    string cf = 6;
    uint64 ttl = 7;
}

However, after setting the TTL, it did not take effect. What could be the issue?

| username: Lucien-卢西恩 | Original post link

This only takes effect for new clusters. Refer to the documentation: TiKV 配置文件描述 | PingCAP 文档中心

| username: system | Original post link

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.