-
Notifications
You must be signed in to change notification settings - Fork 6
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
High CPU for ruby process: rake jobs:work #41
Comments
The rake process cannot easily be stopped/killed: provisioningengine@ProvisioningEngine:~/ProvisioningEnginev0.5.20_testfolder$ ./stopDelayedJobs.sh
myDelayedJobsPid=6359
kill signal sent for Delayed Jobs (PID=6359)
provisioningengine@ProvisioningEngine:~/ProvisioningEnginev0.5.20_testfolder$ ./stopDelayedJobs.sh
myDelayedJobsPid=6359 It works with provisioningengine@ProvisioningEngine:~/ProvisioningEnginev0.5.20_testfolder$ kill -9 6359
provisioningengine@ProvisioningEngine:~/ProvisioningEnginev0.5.20_testfolder$ kill -9 6359
-bash: kill: (6359) - No such process |
The problem seems to be known. See collectiveidea/delayed_job#823, which points to collectiveidea/delayed_job#776. The workaround is supposed to be config.cache_classes = true Let us try that out. |
$ grep -r cache_classes config/environments/
config/environments/test.rb: config.cache_classes = true
config/environments/development.rb: config.cache_classes = false
config/environments/production.rb: config.cache_classes = true TODO:
|
TODO 1) done: Login to CSL9_ProvisioningEngine_Ruby. Before changes: $ ps -p 30019 -o %cpu,%mem,cmd
%CPU %MEM CMD
81.1 69.8 ruby /home/provisioningengine/.rbenv/versions/2.2.4/bin/rake jobs:work Then:
$ ./start
Web Portal started: PID=17425
Delayed Jobs started: PID=17489 Finally checking CPU+MEM consumption: $ ps -p 17489 -o %cpu,%mem,cmd
%CPU %MEM CMD
10.2 2.7 ruby /home/provisioningengine/.rbenv/versions/2.2.4/bin/rake jobs:work and some minutes later: $ ps -p 17489 -o %cpu,%mem,cmd
%CPU %MEM CMD
0.7 2.8 ruby /home/provisioningengine/.rbenv/versions/2.2.4/bin/rake jobs:work Now I need to re-check CPU+Memory after some hours/days... |
On the pre-production system, we see:
and:
It seems like the
rake jobs:work
process is consuming 100% CPU, although it does not seem to do anything:The log file is silent for several days, although the script
is redirecting all
rake jobs:work
output to the file.Also there are no current jobs in the queue:
The text was updated successfully, but these errors were encountered: