-
Notifications
You must be signed in to change notification settings - Fork 3
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: Handle
StartBlock
options within Coordinator & Block Streamer (…
…#553) This PR adds support for the updated Registry types, including the new `StartBlock` config option, across the Block Streamer/Coordinator. With `StartBlock`, the logic within Coordinator is much more straight forward - we no longer need to guess whether we should "continue" or "start over", that is build in to the configuration options. This only really affects the handling of Block Streams, the executor flow remains the same: always restart when a new version is published. To summarise the Block Stream synchronisation process: - `StartBlock::Continue` - Resumes process, keeping the current data in the Redis Stream, and start the Block Stream from `last_published_block` - `StartBlock::Latest` - Starts a new process, clears the Redis Stream, starts the Block Stream from the registry version, essentially being latest - `StartBlock::Height(u64)` - Starts a new process, clears the Redis Stream, starts the Block Stream from the height configured Additionally, Accounts/Indexers which have just been migrated, and also streams which have been stopped but have unchanged versions (e.g. after Block Streamer restart), will be treated the same as `StartBlock::Continue`.
- Loading branch information
1 parent
c8ff7d1
commit 2fc8311
Showing
20 changed files
with
1,202 additions
and
1,144 deletions.
There are no files selected for viewing
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
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
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
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
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
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
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
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,3 +1,5 @@ | ||
#![cfg_attr(test, allow(dead_code))] | ||
|
||
const MAX_S3_LIST_REQUESTS: usize = 1000; | ||
|
||
#[cfg(test)] | ||
|
Oops, something went wrong.