Update the known_gaps table for Deadlocks in the Statediffing application #215

New Issue

2022-03-18T12:57:28Z

abdulrabbani00 commented

2022-03-18 12:57:28 +00:00

(Migrated from github.com)

There are might be many cases where vulcanize-geth skips over a block or block range while the application is running and connected to the database. But to start, we will implement the feature of updating the known_gaps table when a deadlock occurs in the writeStateDiffWithRetry function.

The function will try to write the block for x number of times (due to a deadlock).
If after x retries, the block hasn't been written to the database, write it to the known_gaps table.

In the future, we can extend this capability to other features within the statediff service.

There are might be many cases where `vulcanize-geth` skips over a block or block range while the application is running and connected to the database. But to start, we will implement the feature of updating the `known_gaps` table when a deadlock occurs in the `writeStateDiffWithRetry` function. * The function will try to write the block for `x` number of times (due to a deadlock). * If after `x` retries, the block hasn't been written to the database, write it to the `known_gaps` table. In the future, we can extend this capability to other features within the `statediff` service.

Sign in to join this conversation.

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: cerc-io/go-ethereum#215

Update the known_gaps table for Deadlocks in the Statediffing application #215

Update the `known_gaps` table for Deadlocks in the Statediffing application #215