Expired_at in service-gc-safepoint

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

Original topic: service-gc-safepoint中的expired_at

| username: chenhanneu

【TiDB Usage Environment】Production Environment / Testing / PoC
【TiDB Version】
【Reproduction Path】What operations were performed that led to the issue
【Encountered Issue: Problem Phenomenon and Impact】
【Resource Configuration】Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
【Attachments: Screenshots / Logs / Monitoring】

{
  "service_id": "backup-stream-pitr-test-58",
  "expired_at": 1703318915,
  "safe_point": 446512907227758600
},
{
  "service_id": "backup-stream-pitr-test-59",
  "expired_at": 1703318915,
  "safe_point": 446512907227758600
}

service-gc-safepoint:
Used to query the current GC safepoint and service GC safepoint.

How should the value of expired_at in the result be understood?

| username: wangccsy | Original post link

Could it be the timestamp at that time?

| username: 小龙虾爱大龙虾 | Original post link

Guess the timestamp, you see it starts with 170, didn’t we just go from 169 to 170? :joy_cat:

| username: chenhanneu | Original post link

It is a future timestamp:
(root@10.191.76.22@16:51:51)[(none)]> select from_unixtime(1703318915);
±--------------------------+
| from_unixtime(1703318915) |
±--------------------------+
| 2023-12-23 16:08:35 |
±--------------------------+
Indeed, the GC started to advance after 16:00.

| username: dba远航 | Original post link

Expired TSO time

| username: system | Original post link

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