Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Non existent queues leads to high cpu in WPA #53

Closed
alok87 opened this issue Mar 2, 2020 · 0 comments · Fixed by #139
Closed

Non existent queues leads to high cpu in WPA #53

alok87 opened this issue Mar 2, 2020 · 0 comments · Fixed by #139
Labels
bug Something isn't working

Comments

@alok87
Copy link
Contributor

alok87 commented Mar 2, 2020 •
edited
Loading

When the queue specified in WPA is not present, WPA CPU shoots up. Since it continuously tries to find the non existent queue. If there are many non existent queues then the CPU can increase upto 100% cpu limit leading to CPU throttling of the WPA pod and resulting in scaling becoming very slow.

E0302 12:03:44.409670       1 sqs.go:292] Unable to find queue "prod-dx-doctor_appointment_ingest_queue", AWS.SimpleQueueService.NonExistentQueue: The specified queue does not exist for this wsdl version.

Proposed Solutions

  • Retry with a crashloop if the queue does not exist.

  • Put external validation on non existent queue. Not adding validations in WPA because queue creation can happen by an external job. WPA validation should be done by the external service which creates WPA for you.
@alok87 alok87 added the bug Something isn't working label Mar 2, 2020
@alok87 alok87 changed the title Non existent queues causes very high CPU spikes in WPA Non existent queues leads to high cpu in WPA Mar 2, 2020
@alok87 alok87 changed the title Non existent queues leads to high cpu in WPA Non existent queues leads to high cpu(100% k8s cpu limit) in WPA Mar 2, 2020
@alok87 alok87 changed the title Non existent queues leads to high cpu(100% k8s cpu limit) in WPA Non existent queues leads to high cpu in WPA Mar 2, 2020
@alok87 alok87 mentioned this issue Sep 23, 2021
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Slow down wpa on 404 practo/k8s-worker-pod-autoscaler
1 participant
@alok87