Don't report ZK node exists to system.errors when a block was created concurrently by a different replica #46820
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.
Changelog category (leave one):
Changelog entry (a user-readable short description of the changes that goes to CHANGELOG.md):
Example (comes from a CI run):
Logs:
The problems comes from using
zkutil::KeeperMultiException
to extract the path of the first error. Creating azkutil::KeeperMultiException
creates aKeeperException
, which is a DB::Exception and thus reports to system.errors. Since the exception was created only for that operation, I've replaced by the equivalent functions instead.Closes #32997