You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
time="2024-05-09T18:24:36.715Z" level=error msg="could not run ingestion. Retrying" error="error appending ledgers: ledgers not contiguous: expected ledger sequence 51590893 but received 51594383" pid=1
This happens as part of eventStore.IngestEvents()
This happens after loading the in-memory data structures and Core is running.
Root case theories:
Disconnect between the ledger range in the DB and the one obtained from captive core
DB Corruption
Events in-memory data-structure corruption or malfunctioning
The text was updated successfully, but these errors were encountered:
It turns out that the in-memory loading timed out, but the error was ignored (PR coming up)
As a result, the in-memory data-structure didn't get to load the full ledger range from the DB (in the ocurrence above it only loaded up to ledger 51590893 instead of 51594383)
Later, we attempted to continue loading the in-memory data structure from captive core (which we told to start at the DB boundary: 51594383).
Since the in-memory data structure was only loaded up to 51590893 (due to the time out), it resulted in an error.
We should also extend the default ingestion time out.
What version are you using?
21.0.1
What did you do?
Restart rpc (as part of a K8s cluster upgrade)
What did you expect to see?
Ingestion working
What did you see instead?
This happens as part of
eventStore.IngestEvents()
This happens after loading the in-memory data structures and Core is running.
Root case theories:
The text was updated successfully, but these errors were encountered: