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

grafana show pitr lag more than 30m when inject kill one tidb #42419

Closed
Lily2025 opened this issue Mar 21, 2023 · 2 comments · Fixed by #42422
Closed

grafana show pitr lag more than 30m when inject kill one tidb #42419

Lily2025 opened this issue Mar 21, 2023 · 2 comments · Fixed by #42422
Assignees
Labels
component/br This issue is related to BR of TiDB. severity/moderate type/bug The issue is confirmed as a bug.

Comments

@Lily2025
Copy link

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

http://perf.pingcap.net:3000/d/WOw1JWmVk/ha-test-case-detail?orgId=1&refresh=10s&var-case_id=2610659
kill one tidb

2. What did you expect to see? (Required)

pitr lag less than 5m

3. What did you see instead (Required)

grafana show pitr lag more than 30m when inject kill one tidb
image

4. What is your TiDB version? (Required)

git hash:56412f514ecad4209cb0d92878b68644ed94469a

@Lily2025 Lily2025 added the type/bug The issue is confirmed as a bug. label Mar 21, 2023
@Lily2025
Copy link
Author

/type bug
/severity moderate
/assign YuJuncen

@fubinzh
Copy link

fubinzh commented Sep 5, 2024

Tested it with fix:
TiDB rolling restart before the fix:
image

After the fix:
image

[root@upstream-tidb-0 /]# /tidb-server -V
Release Version: v8.4.0-alpha
Edition: Community
Git Commit Hash: b91cb01
Git Branch: heads/refs/tags/v8.4.0-alpha
UTC Build Time: 2024-09-04 11:46:09

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/br This issue is related to BR of TiDB. severity/moderate type/bug The issue is confirmed as a bug.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants