You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
4. What is your TiDB version? (Required)
v4.0.9
The text was updated successfully, but these errors were encountered:
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.
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
4. What is your TiDB version? (Required)
v4.0.9
The text was updated successfully, but these errors were encountered: