Socket creation failed due 24, Too many open files.

Hi,

This might be a stupid thread but I'll take a shoot on it.

I have the max scale production environment described into MXS-415 ticket.
Under high load over database connections (many frontend servers connecting to the database Loadbalancer) - regularity is 1 per day - I get the maxscale error log filled with :

2015-10-21 16:53:03 Error : Failed to create Read Connection Router session.
2015-10-21 16:53:03 Error : Failed to create Read Connection Router session.
2015-10-21 16:53:03 Error: Establishing connection to backend server 10.200.100.153:3306 failed.
Socket creation failed due 24, Too many open files.
2015-10-21 16:53:03 Error: Establishing connection to backend server 10.200.100.152:3306 failed.
Socket creation failed due 24, Too many open files.
2015-10-21 16:53:03 Error : Failed to create Read Connection Router session.
2015-10-21 16:53:03 Error: Establishing connection to backend server 10.200.100.151:3306 failed.
Socket creation failed due 24, Too many open files.
2015-10-21 16:53:03 Error : Failed to create Read Connection Router session.

Now, I have set before and let it run for one day into /etc/security/limits.conf:

• soft nofile 65535
• hard nofile 65535

after which I have restarted the maxscale daemon to pick-up the change.

Question is (didn't do it but I am going to test now as a last resort) should there be included into the init script before daemon start-up the ulimit -HSn 65535 value by default in the standard rpm/deb build the ulimit setting ?

I suppose other folks are using maxsclae in deployments where the load is quite big.

Thanks,
Alex