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.

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

Octopus 0.10.2 / Rails 5.1.5 / Sidekiq workers eventually run out of memory and freeze #521

Open
kjvarga opened this issue May 9, 2019 · 0 comments

Comments

@kjvarga
Copy link

kjvarga commented May 9, 2019

When upgrading to Octopus 0.10.2 using Rails 5.1.5 we notice that our Sidekiq workers after a day or two will stop processing any jobs. The worker machines, which each run 10 threads, are not even accessible by SSH. They run out of memory. So something in the Octopus upgrade causes them to leak memory over time. Unfortunately we cannot upgrade to Rails 5.2 because of #489 issue with Puma.

This is what the worker node metrics look like when the issue happens:
Instances___EC2_Management_Console

Infrastructure_by_New_Relic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant