Show leader version when reporting mismatch in /status/handlingCommands #1779
Conversation
This file contains 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
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.
Details
We are currently seeing a node running in a detached state. It is reporting a 500 error version mismatch in response to
/status/handlingCommandsbut the version printed out there and in/statusexactly matches leader. So likely, it is unable to load_leaderVersion. This adds the leader version to the output so we can verify the bug.Fixed Issues
N/A, discussion from here
Tests
Not sure how to reproduce on dev, open to suggestions
Internal Testing Reminder: when changing bedrock, please compile auth against your new changes