fix(init): add setting to enable durable locks on crdb #7982
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which Problems Are Solved
There were rare cases where Cockroachdb got blocked during runtime of ZITADEL and returned
WRITE_TOO_OLD
-errors to ZITADEL.How the Problems Are Solved
The root cause of the problem is described in this github issue of the database. The workaround provided by the database is enabling the
enable_durable_locking_for_serializable
-flag as described here.Additional Changes
zitadel init
calledsettings
to allow making changes using the admin user.zitadel init
ensures that variables are set.