-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Multiple issues with temporary bootstrap etcd config #7368
Milestone
Comments
brandond
changed the title
Multiple issues with temporary etcd
Multiple issues with temporary bootstrap etcd config
Apr 27, 2023
This was referenced May 9, 2023
Validated on Version:- k3s version v1.27.1+k3s-ad41fb8c (ad41fb8c) - Previous version Commit ID 9980504196ce0cb53c8e04756598d6f8982a5756
- k3s version v1.27.1+k3s-607cbf0a (607cbf0a) (Target commit id version) Commit ID 324ecfc30da9465b13b4bf93ff90abe7adde1527 Environment DetailsInfrastructure Node(s) CPU architecture, OS, and Version: Cluster Configuration: Config.yaml:
Steps to reproduce the issue
Steps to validate the fix
Validation Results:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A recent customer call turned up a few issues with the temporary etcd that runs to extract bootstrap data:
This made it difficult to raise the quota, as the arg was not being passed through properly.
The defrag/alarm clear runs with a short deadline that may not succeed when the datastore is on slower storage.This made it difficult to bring the cluster up with an increased quota, as the defrag operation took 22 seconds to complete which is longer than the deadline allowed for.
This was fixed a while ago; the customer was on v1.23.6 which had a 10 second timeout. This is 30 seconds on current releleases.
As an additional note, defragging on startup isn't always sufficient to recover storage space; in this case we had to compact as well as defrag in order to bring the size down after they filled the datastore by running an etcdctl perf test on it. I'm not sure we need to handle that though.
The text was updated successfully, but these errors were encountered: