[RFC] fix: poller-service locking does not work #8450
Closed
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.
Needs another look once I'm a little more awake, but this could use some testing and feedback.
I have no idea what's up with the original locking, other than it doesn't work. I found #5619, which didn't include a solution either, so I've ripped out the database locking, and replaced it with thread level locking.
It's not a fantastic fix due to the overall structure of the poller service, but it works for me.
After applying this, CPU load has dropped on my less capable switches from between 60-80%, down to ~10%
DO NOT DELETE THIS TEXT
Please note
Testers
If you would like to test this pull request then please run:
./scripts/github-apply <pr_id>
, i.e./scripts/github-apply 5926