However, after I subscribe with {"jsonrpc": "2.0","id":2,"method":"eth_subscribe","params":["newHeads"]} on websocket, I noticed that there's ~50 blocks lagging compared to arbiscan.io and the logs on the nitro-node seem to show that the blocks in my local node itself are up to date, indicating that the RPC subscription only receive blocks are ~50 behind (I judge this through its log created block l2Block=<block.number> l2BlockHash= where actually is up to date compared to arbiscan.io
`
I run it on 2TB SSD with 32GB RAM, which shouldn't have issues catching up? Is this a bug or I missed anything here?
I ran full node as following https://docs.arbitrum.io/node-running/how-tos/running-a-full-node
However, after I subscribe with actually is up to date compared to arbiscan.io
{"jsonrpc": "2.0","id":2,"method":"eth_subscribe","params":["newHeads"]}on websocket, I noticed that there's ~50 blocks lagging compared to arbiscan.io and the logs on the nitro-node seem to show that the blocks in my local node itself are up to date, indicating that the RPC subscription only receive blocks are ~50 behind (I judge this through its logcreated block l2Block=<block.number> l2BlockHash=where` I run it on 2TB SSD with 32GB RAM, which shouldn't have issues catching up? Is this a bug or I missed anything here?