-
-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix:polaris config watch #3082
fix:polaris config watch #3082
Conversation
…articularly in situations when config events are closed.
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## main #3082 +/- ##
=======================================
Coverage 84.28% 84.28%
=======================================
Files 88 88
Lines 3984 3984
=======================================
Hits 3358 3358
Misses 449 449
Partials 177 177 ☔ View full report in Codecov by Sentry. |
…articularly in situations when config events are closed.
…ix/polaris_config_watch
3f79526
Description (what this PR does / why we need it):
The high CPU usage issue caused by watching the Polaris config, particularly in situations when config events are closed.
If the configuration connection has already been closed, the configuration file monitoring should be canceled.
Otherwise, the following method call will enter into an infinite loop. It is necessary to throw a connection-closed exception to cancel the monitoring.
filePath:config/config.go
filePath: contrib/polaris/config.go