Bug 1319355

Summary:	log aggregation setup should indicate unit examples
Product:	OpenShift Container Platform	Reporter:	Erik M Jacobs <ejacobs>
Component:	Documentation	Assignee:	Vikram Goyal <vigoyal>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Vikram Goyal <vigoyal>
Severity:	unspecified	Docs Contact:	Vikram Goyal <vigoyal>
Priority:	unspecified
Version:	3.1.0	CC:	aos-bugs, jokerman, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-29 22:17:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Erik M Jacobs 2016-03-18 23:35:35 UTC

Ours: https://docs.openshift.com/enterprise/latest/install_config/aggregate_logging.html

Amount of RAM to reserve per Elasticsearch instance. The default is 8GB, and it must be at least 512MB.

Upstream: https://github.com/openshift/origin-aggregated-logging/tree/master/deployment

ES_INSTANCE_RAM: Amount of RAM to reserve per ElasticSearch instance (e.g. 1024M, 2G). Defaults to 8GB; must be at least 512M (Ref.: ElasticSearch documentation.

Comment 1 Vikram Goyal 2017-12-29 22:17:29 UTC

This was fixed here: https://docs.openshift.com/container-platform/3.7/install_config/aggregate_logging.html#aggregate-logging-ansible-variables.

Closing this bug.