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.

Sign up for GitHub

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

Jump to bottom

Skaled not starts from the catchup for a long time after recreation of skaled-container #1373

Open
2 tasks
DmytroNazarenko opened this issue Jan 27, 2023 · 2 comments · Fixed by #2093 · May be fixed by skalenetwork/skale-admin#1143
Open
2 tasks

Skaled not starts from the catchup for a long time after recreation of skaled-container #1373

DmytroNazarenko opened this issue Jan 27, 2023 · 2 comments · Fixed by #2093 · May be fixed by skalenetwork/skale-admin#1143
Assignees
@badrogger
Milestone
SKALE 4.0

Comments

@DmytroNazarenko
Copy link
Collaborator

DmytroNazarenko commented Jan 27, 2023 •
edited by PolinaKiporenko
Loading

Versions
Skaled: skalenetwork/schain:3.16.0-beta.6

Environment
20 active nodes on the network
8 schains up and running

Preconditions
Load tests with blockchain-killer (1 GB of state in use)

Steps to Reproduce/Description

  1. Restart one of the nodes from the catchup from 0 block - 15 other nodes are active and under simple load 2-3 txs per block
  2. check sklaed logs

Expected behavior
Skaled should start catching up blocks in 2-5 minutes after creation.

Actual result
Skaled could not catchup blocks after 10-12 minutes of downtime and may be restarted by skale admin

skaled_not_catchup.log

Tasks
Preview Give feedback
@DmytroNazarenko DmytroNazarenko changed the title Internal issue #670 Skaled not starts from the catchup for a long time after recreation of skaled-container Apr 3, 2023
@DmytroNazarenko DmytroNazarenko added the bug Something isn't working label Apr 3, 2023
@DmytroNazarenko DmytroNazarenko added this to the SKALE 2.5 milestone Aug 1, 2024
@DmytroNazarenko
Copy link
Collaborator Author

Reproduced on mainnet:
skale-node: 3.0.0
skaled: 3.19.0

@dimalit
Copy link
Contributor

dimalit commented Aug 20, 2024

In the provided log, skaled shows first message related to catch-up after 9 minutes of work:

[2023-01-27 18:39:14.594] [14:catchup] [info] 0:CATCHUP_GOT_BLOCKS:COUNT:12968:STARTBLOCK:1

is this wrong? is there any limit on this time?

@PolinaKiporenko PolinaKiporenko assigned kladkogex and unassigned dimalit Aug 27, 2024
@PolinaKiporenko PolinaKiporenko modified the milestones: SKALE 3.1, SKALE 3.1.1 Oct 2, 2024
@PolinaKiporenko PolinaKiporenko moved this from Ready For Pickup to To Do in SKALE Engineering 🚀 Oct 10, 2024
@PolinaKiporenko PolinaKiporenko moved this from To Do to In Progress in SKALE Engineering 🚀 Jan 6, 2025
@PolinaKiporenko PolinaKiporenko moved this from In Progress to To Do in SKALE Engineering 🚀 Jan 15, 2025
@PolinaKiporenko PolinaKiporenko removed the bug Something isn't working label Jan 16, 2025
@PolinaKiporenko PolinaKiporenko moved this from To Do to In Progress in SKALE Engineering 🚀 Jan 23, 2025
This was linked to pull requests Jan 29, 2025
Do not increase failed_rpc_count when Rpc status is False skalenetwork/skale-admin#1143
Open
Reset subsystem status #2093
Merged
@PolinaKiporenko PolinaKiporenko moved this from In Progress to Code Review in SKALE Engineering 🚀 Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@badrogger badrogger

Labels
None yet
Projects
SKALE Engineering 🚀
Status: Code Review
Milestone
SKALE 4.0
5 participants
@dimalit @badrogger @kladkogex @DmytroNazarenko @PolinaKiporenko