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

Do not send new payloads to backward sync if initial sync is in progress #4720

Merged
merged 9 commits into from
Nov 25, 2022

Conversation

fab-10
Copy link
Contributor

@fab-10 fab-10 commented Nov 22, 2022

Signed-off-by: Fabio Di Fabio fabio.difabio@consensys.net

PR description

Do not send new payloads to backward sync if initial sync is in progress, since repivoting the initial sync will be very close to the chain head at the end, and so storing new payloads in the backward sync chain has no advantages, and only consumes resources, since most of them will be ignored when the backwars sync starts after the initial sync.

Fixed Issue(s)

Documentation

  • I thought about documentation and added the doc-change-required label to this PR if
    updates are required.

Changelog

Signed-off-by: Fabio Di Fabio <fabio.difabio@consensys.net>
Signed-off-by: Fabio Di Fabio <fabio.difabio@consensys.net>
Signed-off-by: Fabio Di Fabio <fabio.difabio@consensys.net>
@fab-10 fab-10 changed the title Do not involve backward sync until initial sync os done Do not send new payloads to backward sync if initial sync is in progress Nov 22, 2022
@fab-10 fab-10 self-assigned this Nov 22, 2022
@fab-10 fab-10 added the syncing label Nov 22, 2022
Signed-off-by: Fabio Di Fabio <fabio.difabio@consensys.net>
@@ -433,20 +419,16 @@
}
}

static class Status {
class Status {

Check notice

Code scanning / CodeQL

Inner class could be static

Status could be made static, since the enclosing instance is used only in its constructor.
@fab-10 fab-10 marked this pull request as ready for review November 22, 2022 16:37
@fab-10 fab-10 force-pushed the bwsync-only-after-initial-sync branch from 8494104 to 4d4b89a Compare November 23, 2022 10:22
Signed-off-by: Fabio Di Fabio <fabio.difabio@consensys.net>
@fab-10 fab-10 force-pushed the bwsync-only-after-initial-sync branch from 4d4b89a to 31bfdcd Compare November 23, 2022 10:37
Copy link
Contributor

@macfarla macfarla left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@macfarla macfarla merged commit 2ee204c into hyperledger:main Nov 25, 2022
@fab-10 fab-10 deleted the bwsync-only-after-initial-sync branch November 25, 2022 09:39
macfarla pushed a commit to jflo/besu that referenced this pull request Jan 10, 2023
…ess (hyperledger#4720)

* Do not involve backward sync until initial sync is done

Signed-off-by: Fabio Di Fabio <fabio.difabio@consensys.net>
Signed-off-by: Sally MacFarlane <macfarla.github@gmail.com>
eum602 pushed a commit to lacchain/besu that referenced this pull request Nov 3, 2023
…ess (hyperledger#4720)

* Do not involve backward sync until initial sync is done

Signed-off-by: Fabio Di Fabio <fabio.difabio@consensys.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants