Redis require nofile set to at least 10032 to start correctly
Bug #1635334 reported by
Luca Lorenzetto
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Michele Baldessari |
Bug Description
In a tripleo HA setup on RHEL 7 (custom built images), redis was not starting correctly and failing the cluster service.
After some debugging, limits value has been set to nofile 10032 (both soft/hard).
The service then has started correctly.
I think during image build or deployment a configuration in /etc/security/
To post a comment you must log in.
Thanks Luca!
So we normally have these limits set in systemd config overrides: -controller- 0 limits.d]# more /etc/systemd/ system/ redis.service. d/limit. conf [Service]
[root@overcloud
LimitNOFILE=10240
/etc/systemd/ system/ redis-sentinel. service. d/limit. conf
[Service]
LimitNOFILE=10240
But the problem is that we are currently using the OCF resource to manage redis master/slave via pacemaker. So those settings won't actually do anything (OCF does not invoke systemd). We do the same in puppetlabs-rabbitmq where the puppet module configures the limits in /etc/security/ limits. d.
I see that the current puppet-redis module does not do that out of the box so we will need to:
A) Check if they can add that
B) Provide a workaround in the puppet-tripleo profile