[Node Operator Question] Optimism Mainnet Node RPC issues: block delays and batched blocks

[wrinkledeth]

Are you running the most up to date node software?

• Yes

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

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

[imtipi]

when do you screenshot this?
op mainnet produce blocks every 2 sec,you can get same block number in 2sec, and possible longer depend on network conditions(the sync)

[wrinkledeth]

This was screenshotted a few days ago. I get a block number every 2 seconds on other RPC's (alchemy). The node that I sync'd above usually produces a block every 2 seconds, but every ~30 seconds or so, I get the above lag, and the batched blocks type of odd behavior. Any ideas?

[Chomtana]

Do you notice such a delay on op-node too?

curl -X POST -H "Content-Type: application/json" http://127.0.0.1:8547 --data '{"jsonrpc":"2.0","method":"optimism_syncStatus","params":[],"id":1}' | jq

This command should query op-node status including block number that should be matched with op-geth

[wrinkledeth]

I ended up doing a resync and the problem went away. I will update this thread again with better logs if I ever notice the same issue.