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

Besu can't backward sync after a restart. #8072

Open
jflo opened this issue Dec 29, 2024 · 3 comments
Open

Besu can't backward sync after a restart. #8072

jflo opened this issue Dec 29, 2024 · 3 comments
Labels
bug Something isn't working P3 Medium (ex: JSON-RPC request not working with a specific client library due to loose spec assumtion) snack Smaller coding task - less than a day for an experienced dev ux

Comments

@jflo
Copy link
Contributor

jflo commented Dec 29, 2024

Some kind of race condition seems to be preventing a backward sync session from running with 0 peers. This happened on holesky, after a system restart.

{"@timestamp":"2024-12-28T20:08:03,302","level":"INFO","thread":"vert.x-worker-thread-0","class":"BackwardSyncContext","message":"Starting a new backward sync session","throwable":""}
2024-12-28T20:08:03.312955761Z vert.x-worker-thread-0 WARN found 2 argument placeholders, but provided 3 for pattern `Unable to retrieve block {} from any peer, with {} peers available. Could be a reorged block. Waiting for the next block from t
he consensus client to try again.`
{"@timestamp":"2024-12-28T20:08:03,313","level":"WARN","thread":"vert.x-worker-thread-0","class":"BackwardSyncAlgorithm","message":"Unable to retrieve block 0x41b13c8b0dc2c17c84d9e5c309d865bf91c50aa1bacd570851df46b8728affb9 from any peer, with 0
 peers available. Could be a reorged block. Waiting for the next block from the consensus client to try again.","throwable":""}
{"@timestamp":"2024-12-28T20:08:03,313","level":"INFO","thread":"vert.x-worker-thread-0","class":"BackwardSyncAlgorithm","message":"Current backward sync session is done","throwable":""}
{"@timestamp":"2024-12-28T20:25:50,995","level":"WARN","thread":"vert.x-worker-thread-0","class":"MergeCoordinator","message":"Internal error, backward sync completed but failed to import finalized block 0x1d7358ec1e6f38cad3fe71894de010c7110c03f
a2cbd287de1e2acb01586090e","throwable":""}

Restarting the consensus client (teku) did not help.
Restarting besu did fix it.

@jflo jflo added the bug Something isn't working label Dec 29, 2024
@siladu
Copy link
Contributor

siladu commented Dec 30, 2024

BWS requires at least 1 peer to download the block from so I think failure is expected behaviour: the BWS algorithm will keep starting a new session and retrying until there's an EL peer it can download from. We could tidy up the UX for this scenario though.

@macfarla macfarla added P3 Medium (ex: JSON-RPC request not working with a specific client library due to loose spec assumtion) snack Smaller coding task - less than a day for an experienced dev ux labels Jan 6, 2025
@macfarla
Copy link
Contributor

macfarla commented Jan 6, 2025

suggestion - BWS should wait until peers are available, OR modify the log to say "restarting BWS because 0 peers"

@macfarla
Copy link
Contributor

macfarla commented Jan 6, 2025

also should fix this - wrong number of args to log msg
2024-12-28T20:08:03.312955761Z vert.x-worker-thread-0 WARN found 2 argument placeholders, but provided 3 for pattern `Unable to retrieve block {} from any peer, with {} peers available. Could be a reorged block. Waiting for the next block from t

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P3 Medium (ex: JSON-RPC request not working with a specific client library due to loose spec assumtion) snack Smaller coding task - less than a day for an experienced dev ux
Projects
None yet
Development

No branches or pull requests

3 participants