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
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).
The text was updated successfully, but these errors were encountered:
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).
The text was updated successfully, but these errors were encountered: