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
v1.12 What version of TiDB Operator are you using?
the latest release version What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
What's the status of the TiDB cluster pods?
What did you do?
Prepare a k8s cluster that can only deploy three tikv instances
Simulate a tikv instance failure and let the operator perform a failover operation
At this point, the fourth tikv instance added by failover is the pending status
Restore the previous tikv instance and then set the tidbcluster's .Status.TiKV.FailureStores to empty
What did you expect to see?
When set the .Status.TiKV.FailureStores to empty, tidb-operator should scale in the tikv instances to the original value set by a user
What did you see instead?
The number of tikv instances is still four, not scale in three
The text was updated successfully, but these errors were encountered:
Bug Report
What version of Kubernetes are you using?
v1.12
What version of TiDB Operator are you using?
the latest release version
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
What's the status of the TiDB cluster pods?
What did you do?
.Status.TiKV.FailureStores
to emptyWhat did you expect to see?
When set the
.Status.TiKV.FailureStores
to empty, tidb-operator should scale in the tikv instances to the original value set by a userWhat did you see instead?
The number of tikv instances is still four, not scale in three
The text was updated successfully, but these errors were encountered: