[Node Operator Question] Optimism Mainnet Node RPC issues: block delays and batched blocks #597
Unanswered
wrinkledeth
asked this question in
Node Operators
Replies: 2 comments 2 replies
-
when do you screenshot this? |
Beta Was this translation helpful? Give feedback.
1 reply
-
Do you notice such a delay on op-node too?
This command should query op-node status including block number that should be matched with op-geth |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Are you running the most up to date node software?
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
I followed this guide and was able to sync an optimism mainnet node using op-node / op-geth.
when making rpc requests, very often, the node will "hang", and get stuck on the same block, and then all of a sudden batch together all of the pending blocks and jump ahead
here is a sample to explain what I mean
I fetched the latest block number every ~4 seconds in the above example
Do you know how I can solve /debug this issue? CPU, MEM, and disk consumption is low and normal
Protocol Description
op-geth:v1.101408.0
op-node:v1.9.1
network name: OP Mainnet
Chainid: 10
L1 Chain: Eth Mainnet
Node Logs
No response
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions