Bug #22338
closedWorkers go missing under heavy load
Description
Cloned from BZ:
I just merged a patch to fix this issue upstream:
https://github.com/pulp/pulp/pull/3245
This patch adds a config variable in the tasks section of /etc/pulp/server.conf called 'worker_timeout' that sets the maximum time a worker will run without checking in before it's killed. It also adds some warnings that will get raised before this point to indicate that heartbeats are taking too long.
The one thing I think Katello/Satellite should do is raise the worker_timeout setting. Since installations typically run multiple apps/dbs/processes, it'll probably need a higher timeout than just Pulp alone. The default is 30. I'd probably recommend at least 60. If you plan to support mongoDB running on spinning disks (probably not a good idea) then I'd go with 300.
Let me know if you have any questions.
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/puppet-pulp/pull/299 added
Updated by The Foreman Bot over 6 years ago
- Pull request https://github.com/theforeman/puppet-foreman_proxy_content/pull/156 added
Updated by The Foreman Bot over 6 years ago
- Pull request https://github.com/theforeman/puppet-katello/pull/231 added
Updated by Chris Roberts over 6 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset puppet-pulp|84c0033586861c5f165da9004c1e3e24d0165908.
Updated by Eric Helms over 6 years ago
- Translation missing: en.field_release deleted (
114)
Updated by Justin Sherrill over 6 years ago
- Translation missing: en.field_release set to 284