extra logs during commit #146
Merged
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
ValarDragon
reviewed
Mar 21, 2022
Co-authored-by: Dev Ojha <[email protected]>
ValarDragon
approved these changes
Mar 21, 2022
Created issue: #148 Adding this to the database stability epic so that it is not missed |
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.
Description
This is to help with root causing: osmosis-labs/osmosis#1090
Currently, the provided logs are inconclusive. So far I can only tell that the faulty node ends up with an app hash that is different from the rest of the network. These extra logs should, hopefully, help us understand which store exactly has a different hash from the rest of the network. Also, if there is any relationship to pruning.