You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our Discourse instances are frequently failing health checks. After digging up the root cause, it would seem Sidekiq memory usage would be (at least one of) the culprit:
Sidekiq is consuming too much memory (using: 597.82M) for 'discourse.ubuntu.com', restarting
Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:host=>"REDACTED", :port=>6379, :namespace=>"sidekiq"}
[...]
Detected rogue Sidekiq pid 418761 mem 588632064, killing
Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:host=>"REDACTED", :port=>6379, :namespace=>"sidekiq"}
The workaround is to up the maximum memory through setting the UNICORN_SIDEKIQ_MAX_RSS environment variable to 1000, thus allowing 1GB instead of 500MB default per:
Enhancement Proposal
Hi,
Our Discourse instances are frequently failing health checks. After digging up the root cause, it would seem Sidekiq memory usage would be (at least one of) the culprit:
This is a well-known issue in the community:
https://meta.discourse.org/t/sidekiq-is-consuming-too-much-memory/280933
https://meta.discourse.org/t/sidekiq-is-consuming-too-much-memory-restarting/48395/36
The workaround is to up the maximum memory through setting the
UNICORN_SIDEKIQ_MAX_RSS
environment variable to1000
, thus allowing 1GB instead of 500MB default per:A workaround this issue is to manually set the environment variable in the deployment, by updating the
statefulset
with:Would it be possible to add a charm option to achieve this behavior?
Thank you!
The text was updated successfully, but these errors were encountered: