Skip to content
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

Implement synchronous history backfilling #203

Open
2opremio opened this issue Jun 6, 2024 · 2 comments
Open

Implement synchronous history backfilling #203

2opremio opened this issue Jun 6, 2024 · 2 comments
Assignees

Comments

@2opremio
Copy link
Contributor

2opremio commented Jun 6, 2024

As part of #196 , the wanted history window may be smaller than the existing window.

As part of this task we should create an offline ingestor (e.g. not real time) which backfills range of ledgers. The orchestration of what ledgers to ingest should be part of #202

The ingestor should (together with the orchestrator) to make sure no inconsistencies are left on the database.

In particular, it should ingest ledgers backwards, to ensure that no gaps are left on the database:

image

@2opremio
Copy link
Contributor Author

Reopening as part of the backfill history

@mollykarcher
Copy link
Contributor

See #323

@Shaptic Shaptic changed the title Implement offline ingestor Implement synchronous history backfilling Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

No branches or pull requests

3 participants