-
Notifications
You must be signed in to change notification settings - Fork 2.3k
fix: reload close channel #6916
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
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Sergii Kuzko <[email protected]>
Signed-off-by: Sergii Kuzko <[email protected]>
Signed-off-by: Sergii Kuzko <[email protected]>
Signed-off-by: Sergii Kuzko <[email protected]>
Signed-off-by: Sergii Kuzko <[email protected]>
be29904 to
ceb6c89
Compare
Signed-off-by: Sergii Kuzko <[email protected]>
Signed-off-by: Sergii Kuzko <[email protected]>
|
I cant put my finger on the significance of these changes. Palpably, what problem do these changes resolve? |
I don't see how this code changes the behavior. It looks like go routines were closed before, and they are still closed after these changes. Can you show how in the previous code that the go routines were not closed? |
1. Why is this pull request needed and what does it do?
This pull request introduces improvements to the reload functionality of CoreDNS. It refines the logic for periodically checking for changes in the Corefile configuration and enhances the shutdown procedure for the reload goroutine. Specifically, it:
chan struct{}to signal the reload routine to stop.onInstanceStartuphook.2. Which issues (if any) are related?
This PR addresses the need for a more robust and synchronized reload mechanism in CoreDNS, improving overall stability.
The problem remains #6646 #6645
3. Which documentation changes (if any) need to be made?
No documentation changes are needed.
4. Does this introduce a backward incompatible change or deprecation?
No, this pull request does not introduce any backward incompatible changes or deprecations. It enhances existing functionality while maintaining compatibility with current configurations.