smartcontracts / simple-optimism-node

The easiest way to run an Optimism node
MIT License
324 stars 111 forks source link

Slow syncing after upgrading to latest versions #152

Open breezytm opened 2 months ago

breezytm commented 2 months ago

Our nodes have been online for at least a year and have been working just fine. We recently upgraded to the following versions, and since then, the slow syncing began. I know of another provider who is also having similar issues with his nodes, which makes it clear that this issue is not specific to us. I am wondering if anyone else is experiencing the same issue.

op-geth:v1.101315.2 op-node:v1.7.7

Deployment

    command:
      - --op-network=$NETWORK_NAME
      - --datadir=/geth
      - --http
      - --http.corsdomain=*
      - --http.vhosts=*
      - --http.addr=0.0.0.0
      - --http.port=8545
      - --http.api=web3,debug,eth,txpool,net,engine
      - --ws
      - --ws.addr=0.0.0.0
      - --ws.port=8546
      - --ws.origins=*
      - --ws.api=debug,eth,txpool,net,engine,web3
      - --syncmode=$OP_GETH__SYNCMODE
      - --gcmode=$NODE_TYPE
      - --authrpc.vhosts=*
      - --authrpc.addr=0.0.0.0
      - --authrpc.port=8551
      - --authrpc.jwtsecret=/shared/jwt.txt
      - --rollup.sequencerhttp=${BEDROCK_SEQUENCER_HTTP:-https://mainnet-sequencer.optimism.io}
      - --rollup.disabletxpoolgossip=true
      - --rollup.historicalrpc=$OP_GETH__HISTORICAL_RPC
      - --port=${PORT__OP_GETH_P2P:-39393}
      - --discovery.port=${PORT__OP_GETH_P2P:-39393}

Variables

  NODE_TYPE=archive
  OP_GETH__SYNCMODE=full
breezytm commented 2 months ago

Additional information: They have been trailing by ~21,700 blocks for the past 3 days.