Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Noisy min-resolved-ts logs when the PD default configuration is min-resolved-ts-persistence-interval=0 #44412

Closed
HuSharp opened this issue Jun 5, 2023 · 0 comments · Fixed by #44413

Comments

@HuSharp
Copy link
Contributor

HuSharp commented Jun 5, 2023

Bug Report

#43737 introduced a new approach to getting the min-resolved-ts from the PD server by HTTP API. However, 6.1 pd developed the min-resolved-ts collection feature, but the default configuration is min-resolved-ts-persistence-interval=0, that is, off state, subsequent versions to open, which led to 6.1 upgrade to 6.5/7.0/7.1 this configuration is off state, before 7.1 Before 7.1, tidb did not rely on this feature of pd, 7.1 became dependent on this feature, but for the 6.1 upgrade to 7.1 cluster, pd this feature is turned off by default, so brush this error.

img_v2_e8f3b863-e07b-4830-869f-d26dcab291ag

But this should not affect the normal use of tidb, because pd does not provide this function, tidb will use the previous path

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants