-
Notifications
You must be signed in to change notification settings - Fork 498
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
TiDB operator cannot update configuration for TiKV #5729
Comments
https://docs.pingcap.com/tidb/stable/tikv-configuration-file#engine-new-in-v660
But as you said, reject it explicitly is better |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
What version of Kubernetes are you using?
1.28.1
What version of TiDB Operator are you using?
1.6.0
What storage classes exist in the Kubernetes cluster and what are used for PD/TiKV pods?
standard
What's the status of the TiDB cluster pods?
What did you do?
We tried to change the
storage.engine
option of TiKV, via thespec.tikv.config
property. But we found that after changingstorage.engine
fromraft-kv
topartitioned-raft-kv
, the TiKV keeps usingraft-kv
as the storage engine.spec.tikv.config.storage.engine
topartitioned-raft-kv
raft-kv
What did you expect to see?
Storage engine should be updated, or the config change should be rejected explicitly.
What did you see instead?
Although the Pods are rolling restarted with the updated ConfigMap, the actual configuration being used by the TiKV is not updated. We suspect that the updated configuration gets lost when the TiDB merges the configuration.
The text was updated successfully, but these errors were encountered: