Closed rjx18 closed 2 years ago
I have fixed the error on my end by setting GRAPH_ETHEREUM_MAX_BLOCK_RANGE_SIZE to 100. But it would be good to know what exactly is the maximum block range supported for the RPC endpoints? Thank you!
there was a firewall timeout that was set too low. can you try it again at 1000 and 2000? Thanks.
Yeah we just changed the timeout config. Please let us know if you still get the 502 error when you run the query with 2000 blocks.
Hello! Yes, it seems the error 502 on the testnet RPC endpoint is fixed, but now I get an error 524 when querying 1000 blocks. The error 502 is still there on the mainnet RPC I believe.
We'll take a look at the Testnet. We'll update the Mainnet infrastructure once we verify the changes on the Testnet. Thanks!
Hello! Just wanted to let you know that I've been getting a 502 Bad Gateway error when calling eth_getLogs over a 1000 block range, on the testnet RPC adaptor (https://eth-rpc-api-testnet.thetatoken.org/rpc).
This is on my Graph node indexer that is trying to sync the logs from blocks into my GraphQL database. This worked perfectly fine previously, so I'm wondering what is causing the error here. Querying over blocks with a very small range (30-50 blocks) returns fine, but takes a really long time (14+ seconds). However, not being able to query logs with a range of at most 2000 blocks breaks the graph node indexer, because it tries to query 1, 10, 100, 1000 then 2000 blocks at once when rebuilding the index.
Any ideas? Thank you!