-
Notifications
You must be signed in to change notification settings - Fork 22
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
sr cleanup is too dangerous #187
Comments
this bug mostly affects pxatx, which is running 2.17 or earlier... all other systems have explicit protection for xpublic, which is the biggest problem. However sr.py is rewritten in #174, and in there, there is no implementation of sr cleanup (it has been removed.) losing the function is actually an intermediate step. The rewritten sr.py creates a global state data structure, which makes it possible to do a safe version of cleanup (because it looks at all configurations, not just one at a time) and will delete only if none of the configs reference the exchange. This will help with exchanges that don´t have a special name, like xwinnow, etc... that might fall victim to the same symptom. So there are some necessary steps to making sr cleanup safe, using the new implementation:
|
note we have had two occurrences of deletion of bindings on xpublic on important pumps, and this caused considerable havoc. however current versions explicitly exclude xpublic from cleanup. so the severity of the defect at this time is not high. |
The declare should likely also use the logic above... the current implementation from #174 still spawns processes to do declare, getting global state as above would allow for a much improved declare. |
implemented new config parse for sr.py on issue187 branch. |
dev for this is on https://github.com/MetPX/sarracenia/tree/issue187 |
|
This option is dangerous if involuntary triggered in an operational environment, we may want to add a switch.
The text was updated successfully, but these errors were encountered: