Bug 1700252 - [OSP14]Default ulimit for nova-compute container is too low when ceph is used
Summary: [OSP14]Default ulimit for nova-compute container is too low when ceph is used
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-tripleo-heat-templates
Version: 13.0 (Queens)
Hardware: All
OS: All
medium
medium
Target Milestone: z3
: 14.0 (Rocky)
Assignee: Martin Schuppert
QA Contact: Joe H. Rahme
URL:
Whiteboard:
Depends On: 1693667
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-16 07:49 UTC by Martin Schuppert
Modified: 2019-07-02 20:08 UTC (History)
6 users (show)

Fixed In Version: openstack-tripleo-heat-templates-9.3.1-0.20190314162757.d0a6cb1.el7ost
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1693667
Environment:
Last Closed: 2019-07-02 20:08:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 652076 0 None MERGED Increase DockerNovaComputeUlimit default value 2020-08-27 11:15:12 UTC
Red Hat Product Errata RHBA-2019:1672 0 None None None 2019-07-02 20:08:39 UTC

Description Martin Schuppert 2019-04-16 07:49:03 UTC 
+++ This bug was initially created as a clone of Bug #1693667 +++

Description of problem:

Patch [1] was used to enforce new default ulimit for nova-compute container, it was set to 1024. Though it is possible to adjust this limit, it is still suboptimal for certain use cases: for example, when ceph is configured for ephemeral storage and every instance has a huge number of disks.

In such case default limit is wrong and we have to either adjust it manually using the doc, or change default value. I suggest to increase default value to 1048576 (was configured in RHOSP 12).

Symptom:

237794 <... socket resumed> )     = -1 EMFILE (Too many open files)


[1] https://review.openstack.org/#/c/560991/
Comment 7 errata-xmlrpc 2019-07-02 20:08:28 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:1672
Note You need to log in before you can comment on or make changes to this bug.