Fixed ports_vlans bulk delete from crashing MySQL #11009
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.
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
After you are done testing, you can remove the changes with
./scripts/github-remove
. If there are schema changes, you can ask on discord how to revert.This should fix: https://community.librenms.org/t/vlan-discovery-crashes-mysql-database-after-update-to-v1-43/5394
We've been seeing the same thing where our MySQL instance was restarting twice an hour. So far, 1 hour later it's been stable. Will report back if we see issues.
I chose 50 as an arbitrary number. I couldn't find any data on max size for queries other than packet size which is a per install. We can increase / decrease that number if need to.