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

The Sequencer is taking too long to start. #3636

Open
giskook opened this issue May 18, 2024 · 2 comments
Open

The Sequencer is taking too long to start. #3636

giskook opened this issue May 18, 2024 · 2 comments
Assignees

Comments

@giskook
Copy link

giskook commented May 18, 2024

System information

zkEVM Node version: v0.6.7
OS & Version: Windows/Linux/OSX
Commit hash : (if develop)
Network: Mainnet/Testnet

Expected behaviour

The sequencer‘s startup time should not be too long

Actual behaviour

Some time may take more than 3 minutes (X Layer testnet)

Steps to reproduce the behaviour

Seems related with DS, will reproduce it.

Backtrace

[backtrace]
@zjg555543
Copy link

After multiple retests, but it didn't occur again.

@agnusmor
Copy link
Contributor

agnusmor commented May 22, 2024

Hi, yes, probably it was realted with the update of the datastream file. I don't know if you have enabled datasream after the sequencer was working from some time. If you have done this, the first time sequencer starts after enable datastream it generates the datastream file with all the existing data in the trusted state and this can take some time.

@agnusmor agnusmor self-assigned this May 22, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants