-
Notifications
You must be signed in to change notification settings - Fork 697
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
Potential seq halt risk #3630
Comments
|
It seems increase sequencer's executor's |
Only happend when sequencer set |
I think from this pr: #3604 Way to solve:
X Layer testnet may halt following below configuration:
executor
|
Hi, this is a known issue with the associative cache in executor/prover, to fix it you need to disable it (useAssociativeCache = false) in executor configuration. The prover team is working to fix the issue. |
Our executor do not set |
Executor‘s configure
|
System information
zkEVM Node version:
v0.6.7
OS & Version:
Linux
Commit hash : (-)
Network:
Mainnet/Testnet
Expected behaviour
Actual behaviour
X Layer(node 0.6.7) under load test will halt sequencer
Steps to reproduce the behaviour
Under load test, when create a new l2block, because the prev lock is not proccessed, so the new l2block may halt the sequencer.
Backtrace
node's log (X Layer's, but the logical is the same)
or
executor's log
When submitting logs: please submit them as text and not screenshots.
The text was updated successfully, but these errors were encountered: