unicorn-worker-killer
unicorn-worker-killer copied to clipboard
kzk
Automatically restart Unicorn workers based on 1) max number of requests and 2) max memory
I am running rails 4.1.2 and ruby 2.1.2. I see no oom method error. I can submit more details if you confirm if it working. Thanks.
How do I determine how much memory a unicorn worker is currently using?
When visiting a page that previously would have rendered a 404 page in my rails app, I am now getting a 500 error (after adding unicorn-worker-killer). I get the following...
Not currently sure how to check if the worker killer is working. Also, where can I check the logs of unicorn worker killer?
This PR removes directives for executables, none in this gem, and for test_files which are not used.
- [x] Cover modules with RSpec tests - [x] Restructure monolithic `Unicorn::WorkerKiller` module - [x] Add TravisCI config (support MRI versions since 1.9.3) [](https://travis-ci.org/ViliusLuneckas/unicorn-worker-killer)
Is it possible to provide a logger to the module so that I can keep logs only for unicorn worker killer gem?
We have been using `unicorn worker killer` in our application, however, we need to kill the unicorn worker frequently due to high CPU usages and does not release. It would...
Running Gitlab on a memory-constrained RPI2, where unicorn-worker-killer is used to restart workers after every X requests. Problem is that requests are infrequent and memory leaks accumulate while worker is...
