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

Handle cross-spork access #229

Closed
sideninja opened this issue May 6, 2024 · 0 comments · Fixed by #230
Closed

Handle cross-spork access #229

sideninja opened this issue May 6, 2024 · 0 comments · Fixed by #230
Assignees

Comments

@sideninja
Copy link
Member

Improve the requester client to introduce a wrapper that can switch between hosts for specific height range intervals. This would allow for cross-spork access in case there's such a historic node available.

Furthermore, we should allow for any missed heights to be indexed after the spork, this is in the case where Gateway is done for whatever reason before the spork, and after the spork it should first ingest from the previous spork and then continue with the new spork data. In case this is not possible due to such a node won't be available we should have an emergency flag that allows overwriting new heights (continue from first available in the current spork, but this should only be used on local networks and test networks, never in production).

@sideninja sideninja self-assigned this May 6, 2024
@sideninja sideninja changed the title Handle cross spork access Handle cross-spork access May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

1 participant