-
Notifications
You must be signed in to change notification settings - Fork 13.8k
[FLINK-26797][runtime] Hardens ZKCheckpointIDCounterMultiServersTest #19199
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
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
Contributor
Author
|
The ci run failed due to the debug commit I added: The zookeeper-server.log contain additional debug logs about final requests, e.g. the first getAndIncrement call: I agree that it's a bit verbose. But it should give us a way to see, what actually happened on the ZooKeeper server. |
autophagy
approved these changes
Apr 1, 2022
We only care about monotonically increasing numbers. Unstable connections could cause a retry by the curator client. See FLINK-26120 where a the same error cause was fixed in the same way.
org.apache.zookeeper.server.FinalRequestProcessor provides debug logs for actual operations being performed on the server, which might be interesting to see when investigating test instabilities. The following logs are part of the debug logs: Processing request:: sessionid:0x1003757ccd40000 type:getData cxid:0x11 zxid:0xfffffffffffffffe txntype:unknown reqpath:/flink/default/checkpoint_id_counter ...contains the type of request (e.g. 'getData') and path (e.g. '/flink/default/checkpoint_id_counter').
Contributor
Author
|
Thanks, @autophagy . I removed the debug commit and rebased the branch. I'm gonna go ahead and create backport PRs. |
This was referenced Apr 1, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What is the purpose of the change
There was a connection issue again with ZK that supposedly caused the IDCounter to be incremented once too often.
Brief change log
Verifying this change
A CI run with a forced ZK test failure was added temporarily to verify the log4j configuration changes.
Does this pull request potentially affect one of the following parts:
@Public(Evolving): noDocumentation