-
Notifications
You must be signed in to change notification settings - Fork 275
fix(syncing): make Syncer shutdown idempotent after start failure #3418
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
Open
racequite
wants to merge
1
commit into
evstack:main
Choose a base branch
from
racequite:fix-syncer-idempotent-shutdown
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+101
−3
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
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.
🩺 Stability & Availability | 🔴 Critical | 🏗️ Heavy lift
Serialize startup and shutdown completion.
At Line 189,
StartpublishessyncerLifecycleStartedbefore initialization completes. A concurrentStopcan cancel the context, observe an emptys.wg, and closes.heightInCh.Startcan then starts.raftRetriever, creates.daFollower, or launch workers after shutdown. This can cause sends to a closed channel and leave workers outside the shutdown wait.Stopalso readss.fiRetrieverands.daFollowerwhileStartwrites them withoutlifecycleMu. A secondStopreturns at Line 264 before the first cleanup completes.Add explicit
startingandstoppingstates with a completion signal, or use an equivalent lifecycle gate. Do not allow startup after shutdown begins. Make concurrentStopcallers wait for the first cleanup. Add a concurrent lifecycle test and run it with-race.As per coding guidelines, protect shared state and prevent goroutine leaks.
Also applies to: 261-271
🤖 Prompt for AI Agents
Source: Coding guidelines