| 2014-09-04 16:26:01 |
Julian Klinck |
bug |
|
|
added bug |
| 2014-09-04 16:26:27 |
Julian Klinck |
description |
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:
https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/horizon/templates/zzz_performance_tuning.conf.erb
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 deployment 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:
https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/horizon/templates/zzz_performance_tuning.conf.erb
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. |
|
| 2014-09-04 16:27:03 |
Julian Klinck |
description |
We found out that a fresh deployment 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:
https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/horizon/templates/zzz_performance_tuning.conf.erb
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 deployment 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:
https://github.com/stackforge/fuel-library/blob/master/deployment/puppet/horizon/templates/zzz_performance_tuning.conf.erb
The number of servers and max_clients 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. |
|
| 2014-09-05 09:28:13 |
Dmitry Pyzhov |
fuel: milestone |
|
5.1 |
|
| 2014-09-05 09:28:23 |
Dmitry Pyzhov |
fuel: assignee |
|
Fuel Library Team (fuel-library) |
|
| 2014-09-05 09:43:36 |
Aleksandr Didenko |
fuel: assignee |
Fuel Library Team (fuel-library) |
Aleksandr Didenko (adidenko) |
|
| 2014-09-05 13:51:29 |
Vladimir Kuklin |
fuel: importance |
Undecided |
High |
|
| 2014-09-05 13:51:31 |
Vladimir Kuklin |
fuel: status |
New |
Confirmed |
|
| 2014-09-05 17:56:24 |
Dmitry Borodaenko |
marked as duplicate |
|
1331554 |
|
