Repository navigation
BlockIngestor not recovering from a transient RPC issue #2089
Description
Do you want to request a feature or report a bug?
bug
What is the current behavior?
After a network interruption, or node restart, the BlockIngestor can get into a state where it cannot reconnect with the node.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Dec 19 17:41:51.514 WARN Trying again after block polling failed: Ethereum node took too long to return receipts for block 0xad12…9580, network_name: mainnet, component: BlockIngestor
Dec 19 17:44:52.523 DEBG Trying again after eth_getBlockByNumber(latest) no txs RPC call timed out (attempt #1), network_name: mainnet, component: BlockIngestor
Dec 19 17:47:52.528 DEBG Trying again after eth_getBlockByNumber(latest) no txs RPC call timed out (attempt #2), network_name: mainnet, component: BlockIngestor
Dec 19 17:50:52.534 DEBG Trying again after eth_getBlockByNumber(latest) no txs RPC call timed out (attempt #3), network_name: mainnet, component: BlockIngestor
Dec 19 17:53:52.540 DEBG Trying again after eth_getBlockByNumber(latest) no txs RPC call timed out (attempt #4), network_name: mainnet, component: BlockIngestor```
This is fixed only by a restart.
What is the expected behavior?
BlockIngestor should be able to recover by itself.
Activity
leoyvens commentedon Dec 21, 2020
@madumas did it only log 4 retries and then logged nothing more?
madumas commentedon Dec 21, 2020
It continued until attempt #894, when I restarted graph-node.