Block catch up failed with response too large
SimonBerens opened this issue · comments
Description
Blockscout keeps emitting the same log:
2024-04-26T01:22:56.558 application=indexer fetcher=block_catchup first_block_number=76840 last_block_number=76838 step=receipts [error] failed to fetch: [%{code: -32003, data: %{block_hash: "0x84648d86d9adcc16899e8258eee3feef2e2c71174340c3e106388baf2a74d98a", block_number: 76838, from_address_hash: "0x00000000000000000000000000000000000a4b05", gas: 0, gas_price: 0, hash: "0xae98c55c087ec4f2d805799213755d09d30d8706626dcffaeb3875bf655c2f4c", index: 0, input: "0x6bf6a42d0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000053d7240000000000000000000000000000000000000000000000000000000000012c260000000000000000000000000000000000000000000000000000000000000001", nonce: 0, r: 0, s: 0, to_address_hash: "0x00000000000000000000000000000000000a4b05", transaction_index: 0, type: 106, v: 0, value: 0}, message: "response too large"}, %{code: -32003, data: %{block_hash: "0x84648d86d9adcc16899e8258eee3feef2e2c71174340c3e106388baf2a74d98a", block_number: 76838, from_address_hash: "0xcd0f67b8afd90d2a7d7717aa7e3261f564e17f7f", gas: 19705547, gas_price: 3100000000, hash: "0xaf505e891beddd975e3627484d35a99164a36037619cce086a9a23394f872fc2", index: 1, input: "0x40c10f1900000000000000000000000001c4f77add319d0a6aa4cd660566780e47e8ef880000000000000000000000000000000000000000000000000000000000002710", max_fee_per_gas: 3200000000, max_priority_fee_per_gas: 3000000000, nonce: 8600, r: 68822063260003781631048588946307783225032857498069921220007817383774126426273, s: 38711127757555533123074175607082542706979157525664067683045207587568680688018, to_address_hash: "0x729b4c30d7d0eba0fa3a077cf7d9ee5a49936a00", transaction_index: 1, type: 2, v: 1, value: 0}, message: "response too large"}, %{code: -32003, data: %{block_hash: "0x489a297e58e57410d191fa5723039cfd6179850da88447f4e730b6e816543e90", block_number: 76839, from_address_hash: "0x00000000000000000000000000000000000a4b05", gas: 0, gas_price: 0, hash: "0x83e77eb4e9d028697e3c08fadd9e0d564786360a88ebee2bf0828f00772054de", index: 0, input: "0x6bf6a42d0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000053d7240000000000000000000000000000000000000000000000000000000000012c270000000000000000000000000000000000000000000000000000000000000007", nonce: 0, r: 0, s: 0, to_address_hash: "0x00000000000000000000000000000000000a4b05", transaction_index: 0, type: 106, v: 0, value: 0}, message: "response too large"}]. Retrying.
The key part seems to be the message at the end, response too large. Is there some env variable I can use to configure the maximum allowable response size?
Type of the installation
Helm charts (k8s)
Type of the JSON RPC archive node
Geth
Type of the chain
L2
Link to the page
No response
Steps to reproduce
No response
Backend version
5.2.2
Frontend version
No response
Elixir & Erlang/OTP versions
Elixir 1.14.5 (compiled with Erlang/OTP 25)
Operating system
Linux
Additional information
No response
@SimonBerens you can reduce the number of receipts in the batch via INDEXER_RECEIPTS_BATCH_SIZE runtime variable. The default value is 250.
I am closing this. Please let us know if the issue persists after reducing the default batch size.