Upgrade is fine, TiDB logs show: store min resolved ts not enabled, addr: http://pdip:2379

Translated
1

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

Original topic: 升级没问题，tidb日志刷：store min resolved ts not enabled, addr: http://pdip:2379

| username: 我是咖啡哥

[TiDB Usage Environment] Testing
[TiDB Version] Upgraded from v6.5.0 to v7.1.0
[Reproduction Path] Offline upgrade
[Encountered Issue: Problem Phenomenon and Impact]
The cluster has only one physical machine, and all components are on one server.
Starting version: v6.1.0, upgraded to v6.5.0, no such error occurred. After upgrading to V7.1.0, this log keeps appearing.

image
image1380×286 236 KB

First error:

[2023/06/21 14:23:59.047 +08:00] [ERROR] [pd.go:111] ["store min resolved ts not enabled, addr: http...

The upgrade process was normal. After the upgrade, the tidb log keeps showing the following log:

[2023/06/21 15:18:29.045 +08:00] [ERROR] [pd.go:111] ["store min resolved ts not enabled, addr: http://pdip:2379"]

The cluster status is also normal. The database can also be connected and used normally.
What is the specific reason for this error? How can this error be cleared?

[Resource Configuration]
[Attachments: Screenshots/Logs/Monitoring]

image
image1380×554 336 KB

2
| username: 裤衩儿飞上天 | Original post link

It seems like this is the reason.
I upgraded, and it was 0, but I didn’t run the test, so I didn’t notice this error.

3
| username: 我是咖啡哥 | Original post link

It looks like this is the issue, I’ll try to fix it.

4
| username: 我是咖啡哥 | Original post link

Did I write something wrong here?
I restarted the cluster, why didn’t it take effect?

5
| username: 裤衩儿飞上天 | Original post link

It’s already within the PD range, try removing the PD server.

6
| username: redgame | Original post link

Set enable-min-resolved-ts to true in the PD cluster configuration file pd.toml, and then restart PD.

7
| username: zhanggame1 | Original post link

It’s more trouble to modify it than to delete the old PD and add a new one.

8
| username: 我是咖啡哥 | Original post link

It’s not recommended to directly modify the configuration files on the nodes, right? Such changes seem to be temporary and might get lost.

9
| username: 我是咖啡哥 | Original post link

The first time I changed it, I didn’t add this, and it still didn’t work after the change.

10
| username: 裤衩儿飞上天 | Original post link

I just tried it, and I didn’t succeed either :joy:

11
| username: dba-kit | Original post link

The TiKV configuration also has this parameter. Try adding raftstore.report-min-resolved-ts-interval as well.

12
| username: 我是咖啡哥 | Original post link

raftstore.report-min-resolved-ts-interval, this parameter is checked to be 1s.

13
| username: dba-kit | Original post link

I tried it and it can be modified online: set config pd `pd-server.min-resolved-ts-persistence-interval`= "1s";

14
| username: 我是咖啡哥 | Original post link

Awesome, no errors after modification.
set config pd 'pd-server.min-resolved-ts-persistence-interval' = "1s";

image
image1380×664 296 KB

image
image1314×320 134 KB

15
| username: system | Original post link

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