-
Notifications
You must be signed in to change notification settings - Fork 637
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error while executing unsigned transaction via eth_call #1930
Comments
It fails when it try to make |
Solved the problem with tuning prover configuration like following:
But I don't think it is proper solution, because allocating ~1000 connections to postgres (max_connections) is hard almost any hardware. |
The issue is related to performance as you've already figured out. We're working on improving performance for the different components of the system, and how we deal with scaling. |
@bdrhn9 can you point-out where is setting "dbNumberOfPoolConnections" is located? I get "failed to execute the unsigned transaction:not enough keccak counters to continue the execution" error, when using eth_call. |
Thanks! I did not found it, as it's not included in latest release (https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.0.3-RC36) :) |
Is not reproducible anymore, request executes successfully on production endpoint of mainnet now.
Returns result
I have filed a new issue with a more detailed overview of the problem, as it is not gone for the contracts which have to return a lot of data. |
Hello, I successfully spinned zkevm-node up for testnet. It's fully synced and I'm using current latest release
v0.0.3-RC29
. While I'm trying to read statically on chain data via eth_call my RPC components throws the following error, normally contracts and backend works great on other chains:The text was updated successfully, but these errors were encountered: