Skip to content

[Node Operator Question] op-geth is consistently 12 hours behind #68

Closed Answered by sbvegan
cheneyweb asked this question in Node Operators
Discussion options

You must be logged in to vote

I was able to chat with a couple other client engineers and they noted:

Generating next batch means that the op-node is not seeing batch-data, and generating an alternative chain (with 12-hour delay) to keep it alive without sequencer. But it should really be seeing the batches.

“ignoring batch with mismatching parent hash”: they are seeing batches, but then unable to apply them on top of their previously trusted chain.

  • Their current chain is wrong because the blocks they have are not expected blocks that the new blocks build on top of.
  • They might’ve not accurately recovered from a reorg or it might not have started up correctly given the current chain.
  • Process that warms up derivatio…

Replies: 5 comments 12 replies

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@sbvegan
Comment options

Comment options

You must be logged in to vote
1 reply
@Rogalek
Comment options

Comment options

You must be logged in to vote
10 replies
@sbvegan
Comment options

@Rogalek
Comment options

@sbvegan
Comment options

@sbvegan
Comment options

@Rogalek
Comment options

Answer selected by sbvegan
Comment options

You must be logged in to vote
0 replies
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
node-operator Questions relating to running a rollup node on OP Mainnet/Testnet. discussion-metrics Used by Github Action to gather discussion metrics on the question and answer section.
3 participants