Allow nitro nodes to forward requests based on block number to archive nodes #451
Conversation
|
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. |
arbitrum/config.go
Outdated
| type ArchiveRedirectConfig struct { | ||
| URL string `koanf:"url"` | ||
| Timeout time.Duration `koanf:"timeout"` | ||
| LastBlock uint64 `koanf:"last-block"` | ||
| } |
There was a problem hiding this comment.
Do we see ourselves having archive nodes with an "EarliestBlock" too? If that's the case then we should have that info too. We'd also have to change the pool function.
There was a problem hiding this comment.
Nope we wont be supporting EarliestBlock instead it is assumed the blocks presence is contiguous i.e if i give configs with last blocks as nodeA=100 and nodeB=200 then requests for blocks from classic.last-block to 100 will go to nodeA and 101 to 200 will go to nodeB
| for _, lastBlockAndClient := range a.lastBlockAndClients { | ||
| if blockNum <= lastBlockAndClient.lastBlock { | ||
| return lastBlockAndClient.client | ||
| } | ||
| } |
There was a problem hiding this comment.
Could we have it randomly select within clients that have the same last block? Otherwise it'll always send to the same one.
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-redirectsoption which is a list ofBlockRedirectConfigconsisting of fields-url,timeoutandlast-block(block up to which this archive node can service requests).User can also configure via command line using
block-redirects-listwhich is a string that should be in json format consisting array of above archive node configs.Corresponding nitro PR- OffchainLabs/nitro#3215
part of NIT-3211