[General] L2 blocks stop going up on specific op-batcher configuration #874
tiagorvmartins
started this conversation in
General
Replies: 2 comments 4 replies
-
what altda you use?any logs during l2 production outage?what l1 chain you use?
|
Beta Was this translation helpful? Give feedback.
2 replies
-
Please monitor block production by monitoring the op-node https://docs.optimism.io/operators/node-operators/management/metrics |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Discussion Topic
We have noticed that L2 blocks stop being produced for about 25 minutes to 30 minutes under specific op-batcher flag configurations, and we would like to understand the reason behind it, below you can check each component settings we are using that result in this failure scenario.
op-geth
op-alt-da
op-node
op-batcher
op-proposer
op-challenger
After experimenting different flags on op-batcher, we no longer experience the same issue, we changed op-batcher to the following:
We would like to understand why that is the case?
We thought we could use span batches and increase the target num frames,
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions