Bug 1611788 - [free-int] max virtual memory areas vm.max_map_count [65530] is too low
Summary: [free-int] max virtual memory areas vm.max_map_count [65530] is too low
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.11.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.11.0
Assignee: ewolinet
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-08-02 18:01 UTC by Justin Pierce
Modified: 2018-10-11 07:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-10-11 07:23:07 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Error output from crashing pod (4.63 KB, text/plain)
2018-08-02 18:01 UTC, Justin Pierce 		no flags Details
skipping memory changes (1.24 KB, text/plain)
2018-08-02 19:20 UTC, Justin Pierce 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:2652 0 None None None 2018-10-11 07:23:41 UTC

Description Justin Pierce 2018-08-02 18:01:03 UTC 
Created attachment 1472803 [details]
Error output from crashing pod

Description of problem:
After attempted upgrade to OCP logging 3.11, es pods in crash loop due to memory requirements.

Version-Release number of the following components:
v3.11.0-0.10.0

How reproducible:
Presently occurring in free-int cluster.

Steps to Reproduce:
1. Standard logging upgrade from v3.10 to v3.11.0-0.10.0
Comment 1 Justin Pierce 2018-08-02 19:20:40 UTC 
Created attachment 1472814 [details]
skipping memory changes
Comment 2 ewolinet 2018-08-03 21:52:05 UTC 
fixed by https://github.com/openshift/openshift-ansible/pull/9267
Comment 3 Scott Dodson 2018-08-14 21:24:37 UTC 
Should be in openshift-ansible-3.11.0-0.15.0
Comment 4 Junqi Zhao 2018-08-15 07:34:16 UTC 
vm.max_map_count is 262144 for ES pod, but there is "java.io.IOException: No space left on device" for one ES pod, see Bug 1616169.

Close this defect, ES IO issues will be tracked by Bug 1616169
Comment 6 errata-xmlrpc 2018-10-11 07:23:07 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-2018:2652
Note You need to log in before you can comment on or make changes to this bug.