-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Refactor SnapshotInfo
dataflow in finalization
#124336
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
Refactor SnapshotInfo
dataflow in finalization
#124336
Conversation
There's no need to have a `SnapshotInfo` consumer to run at the end of finalization, we only pass it the value we already calculated earlier. This replaces it with a bare `Runnable` instead.
Pinging @elastic/es-distributed-coordination (Team:Distributed Coordination) |
Small change arising from work towards a fix for #108907 - snapshot finalization is a bit of a tangle of code split across |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
I might change the commit message to say "Refactor" instead of "Clean up" |
SnapshotInfo
dataflow in finalizationSnapshotInfo
dataflow in finalization
There's no need to have a `SnapshotInfo` consumer to run at the end of finalization, we only pass it the value we already calculated earlier. This replaces it with a bare `Runnable` instead.
💚 Backport successful
|
There's no need to have a `SnapshotInfo` consumer to run at the end of finalization, we only pass it the value we already calculated earlier. This replaces it with a bare `Runnable` instead.
There's no need to have a `SnapshotInfo` consumer to run at the end of finalization, we only pass it the value we already calculated earlier. This replaces it with a bare `Runnable` instead.
There's no need to have a
SnapshotInfo
consumer to run at the end offinalization, we only pass it the value we already calculated earlier.
This replaces it with a bare
Runnable
instead.