Skip to content

resequencing takes too long when restarting the sequencer after a stress test. #530

@xzav3r

Description

@xzav3r

Issue Description

I encountered a problem during testing with the rm-executor-zkcounter2 branch.

Steps to Reproduce

  1. Start the node using the make run command.
  2. Perform a stress test using adventure, either native transfers or ERC20 transfers.
  3. Run the stress test with adventure for approximately 5 minutes, then stop the stress test.
  4. Restart the sequencer.

Observed Behavior

Upon restarting the sequencer, it triggers resequencing, which takes an excessively long time (over 20 minutes).
INFO] [05-29|05:54:22.100] [5/13 Execution] ResequenceFromSMTAlignment, last batch 664 is lower than highest batch in datastream 681, resequencing...

Image

Expected Behavior

The resequencing process should complete in a reasonable amount of time after a stress test.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions