Skip to content

Allow nitro nodes to forward requests based on block number to archive nodes #451

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

Merged
merged 6 commits into from
May 23, 2025

Conversation

ganeshvanahalli
Copy link
Contributor

@ganeshvanahalli ganeshvanahalli commented May 6, 2025

This PR allows forwarding of requests to archive nodes based on block numbers thus allowing splitting of archive databases for better manageability. Configured via block-redirects option which is a list of BlockRedirectConfig consisting of fields- url, timeout and last-block (block up to which this archive node can service requests).

User can also configure via command line using block-redirects-list which is a string that should be in json format consisting array of above archive node configs.

--execution.rpc.block-redirects-list=`[{"url": "<>", "timeout":<in nano seconds>, "last-block": 100}, {"url":"<>}]`

Corresponding nitro PR- OffchainLabs/nitro#3215
part of NIT-3211

@joshuacolvin0
Copy link
Member

Requests can come in to any of the nodes, so each node will need to be able to determine which node to forward requests to if needed. So a node that has information for blocks 10,000-20,000 might forward request for block 500 to a node1, and block 21,000 to node 3.

@eljobe eljobe merged commit 21a9408 into master May 23, 2025
14 of 15 checks passed
@eljobe eljobe deleted the enable-forwardingblockrequestsa-archivenodes branch May 23, 2025 09:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants