Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When lighthouse is started without geth, and the searcher's geth node comes online, lighthouse won't trigger sync until 40 minutes after geth is started.
The reason why is discussed at length here:
ethereum/go-ethereum#27482 (comment)
TLDR:
lighthouse will not even attempt sync if EL is not online
once EL is online, lighthouse will do "finalized sync" where it tries to catch up to the finalized checkpoint. during this time, it will not send EL
newPayload
adding the flag makes lighthouse send
newPayload
during finalized sync, so it triggers geth's sync fasterThis flag is officially documented here:
https://github.com/sigp/lighthouse/blob/bf955c7543dac8911a6f6c334b5b3ca4ef728d9c/book/src/help_bn.md?plain=1#L464
Testing:
Lighthouse:
Geth:
Added --disable-quic to not listen on 9001.
Flag documented here: https://github.com/sigp/lighthouse/blob/bf955c7543dac8911a6f6c334b5b3ca4ef728d9c/book/src/help_bn.md?plain=1#L475
Testing: