Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

op-node: persisted sequencer state is not loaded after restart #12854

Open
zhwrd opened this issue Nov 6, 2024 · 0 comments
Open

op-node: persisted sequencer state is not loaded after restart #12854

zhwrd opened this issue Nov 6, 2024 · 0 comments
Labels
A-op-node Area: op-node C-bug Category: bugs

Comments

@zhwrd
Copy link
Contributor

zhwrd commented Nov 6, 2024

Bug Description
The OP_NODE_RPC_ADMIN_STATE flag is used to persist the sequencer state so that sequencer maintains its active state after unexpected restart. This behaviour seems to be broken.

Steps to Reproduce

  1. Set OP_NODE_RPC_ADMIN_STATE to a persistent path
  2. Make admin_startSequencer call to start the sequencer.
  3. Observe that OP_NODE_RPC_ADMIN_STATE/state is updated with {"sequencerStarted":true}
  4. Restart op-node
  5. Observe that the op-node is started with sequencing disabled and that OP_NODE_RPC_ADMIN_STATE/state is updated to {"sequencerStarted":false}

Expected behavior
op-node should load and apply the state stored in OP_NODE_RPC_ADMIN_STATE after restarts

Environment Information:
op-node v1.9.5 (although i think this has been an issue since at least a few 1.9 releases back)

@zhwrd zhwrd added C-bug Category: bugs A-op-node Area: op-node labels Nov 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-op-node Area: op-node C-bug Category: bugs
Projects
None yet
Development

No branches or pull requests

1 participant