Only in HA mode we deploy /etc/security/limits.conf file with higher than standard values (during corosync_setup stage). So on simple CentOS env we also have 1024 files limit, I've just checked on a live env. I don't have a live HA ubuntu env to check, but it also should have 102400 open files limit since we deploy /etc/security/limits.conf file there as well.
In my opinion, the best way to solve this is to include "/etc/default/rabbitmq-server" file in our rabbitmq packages which will have reasonable defaults. This file is being sourced by the current init scripts already, so we just need to add it.
Only in HA mode we deploy /etc/security/ limits. conf file with higher than standard values (during corosync_setup stage). So on simple CentOS env we also have 1024 files limit, I've just checked on a live env. I don't have a live HA ubuntu env to check, but it also should have 102400 open files limit since we deploy /etc/security/ limits. conf file there as well.
In my opinion, the best way to solve this is to include "/etc/default/ rabbitmq- server" file in our rabbitmq packages which will have reasonable defaults. This file is being sourced by the current init scripts already, so we just need to add it.