Open trader-payne opened 7 months ago
So I learned today that Arbitrum Orbit chains only produce a block when there is a transaction. For infrequently used chains, this means very infrequent blocks. Reader will possibly take a long time to be "ready" in this case.
We are working on a fix for this :)
When the 'reader node' was restarted, sometimes relayer would be very slow to detect that it missed a block (and restart...). This is one aspect of this problem, now fixed here: 5d9af0b827aff0753da7666b0a07502020d53dcb.
Firehose reader node is slow to become "ready" after restarts, especially for slow blockchains like Bitcoin. Matthew Darwin suggested a potential fix would be to roll back the last block by 1 in the poller.
You can see in the snippet how long it took to become ready.
As you can see, it took 15 minutes to go back in a working state.
Logs from restart: