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

Latency increased during tidb cluster rolling upgrade #22393

Closed
tennix opened this issue Jan 14, 2021 · 2 comments
Closed

Latency increased during tidb cluster rolling upgrade #22393

tennix opened this issue Jan 14, 2021 · 2 comments
Labels
severity/moderate sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.

Comments

@tennix
Copy link
Member

tennix commented Jan 14, 2021

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)

This is not yet reproduced.

TiDB cluster is deployed in k8s, the original procedure is changing the log level of pd/tikv/tidb configuration, and tidb-operator will roll upgrade the whole cluster.

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

Low latency during rolling upgrade

3. What did you see instead (Required)

A latency spike appeared during TiKV rolling upgrade.
image
image
The application latency also increased to 13s.

Though the TiKV leader from the Grafana did not drop to zero during tikv upgrade. It did drop to zero from PD's monitoring
image

4. What is your TiDB version? (Required)

v4.0.9

@tennix tennix added the type/bug The issue is confirmed as a bug. label Jan 14, 2021
@zyguan
Copy link
Contributor

zyguan commented Dec 30, 2021

No update for a long time, feel free to reopen it if the issue still exists.

@zyguan zyguan closed this as completed Dec 30, 2021
@github-actions
Copy link

Please check whether the issue should be labeled with 'affects-x.y' or 'fixes-x.y.z', and then remove 'needs-more-info' label.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
severity/moderate sig/transaction SIG:Transaction type/bug The issue is confirmed as a bug.
Projects
None yet
Development

No branches or pull requests

3 participants