-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
cli: add command to manually reindex tx and block events (backport: #6676) #9034
Conversation
Note that if #8946 is implemented, it will make reindexing stop working for blocks prior to the latest. That's not necessarily a blocker to doing it, but it's worth considering the interaction. |
ah good point, It seems like the abciresponses would move to a abci.db and be optional to not bloat state.db. For archive nodes they may opt to store those and provide snapshots to others to reindex data. |
This will still be a configurable option. Users will be able to save ABCI responses if they want which will allow them to reindex missed blocks. I assume those running indexers probably care less about minimizing storage. |
Have a test that's not passing because apparently an incorrect connection url is given to the postgres instance but no error is returned when one is expected |
One minor difference here to the original backport is that v0.34 only supports a single indexer whereas v0.35+ supports multiple |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🙃
This is a backport of #6676 which adds a new cli to reindex missed blocks (if the node has the respective ABCIResponses)
This will help node operators who offer indexing service the ability to reindex missed events i.e. in the case their node goes down