-
Notifications
You must be signed in to change notification settings - Fork 307
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
pindexer: error on undefined field #4999
Comments
To aid in debugging, I've uploaded a fresh copy of a raw cometbft event db, in custom postgres format, here: https://artifacts.plinfra.net/penumbra-1/cometbft-dbdump-height-3141978.dump. Plugging that into a local setup will allow rerunning pindexer quickly to 1) reproduce the problem; and 2) try candidate fixes if necessary. |
I was able to reproduce the failure from that dump, although I can't identify where the null field is coming from. Pulled another dump from a different nodes cometbft db, and also encountered a failure at a different block:
which makes me suspect we've got a data integrity issue in the databases. In order to debug we'll need to update the reindexer to support v0.81.x migrations and rebuild from scratch. It's been a long while since we've done that on the dbs in question. |
Prepared a bump for the reindexer in penumbra-zone/reindexer#21, running that code now to get a fresh database. |
Describe the bug
pindexer errors out on mainnet db data due to a missing field
To Reproduce
Steps to reproduce the behavior:
pindexer
(at least v1.0.0) against mainnet events dbExpected behavior
pindexer ingests block 3139617 and continues without error.
Screenshots
Error message:
Additional context
Looks like the problem is caused by slow queries on the target database. Indeed, the database I'm talking to can be quite slow, due to heavy traffic. However, I don't think that's the source of the problem: I think we've got a syntax error in a query. We can rule this out by checking against a local db and verifying that the crash still happens.
The text was updated successfully, but these errors were encountered: