We found out that a fresh deploying of a FUEL controller node with CEPH onto a 24-Core machine with 32GB of memory resulted in a none working object storage. The issue was that the rados-gw service didn't came up "Operation not permitted".
The number of servers and client are such high that we run out of different hard centos system limits (open files, max threads). Reducing the amount of start_servers made rados-gw service working.
Either introduce hard upper boundaries for such auto tuning or increase the system limits, too.
We found out that a fresh deploying of a FUEL controller node with CEPH onto a 24-Core machine with 32GB of memory resulted in a none working object storage. The issue was that the rados-gw service didn't came up "Operation not permitted".
The issue is that apache is too aggressively auto tuned by the script: /github. com/stackforge/ fuel-library/ blob/master/ deployment/ puppet/ horizon/ templates/ zzz_performance _tuning. conf.erb
https:/
The number of servers and client are such high that we run out of different hard centos system limits (open files, max threads). Reducing the amount of start_servers made rados-gw service working.
Either introduce hard upper boundaries for such auto tuning or increase the system limits, too.