1319355 – log aggregation setup should indicate unit examples

Bug 1319355 - log aggregation setup should indicate unit examples

Summary: log aggregation setup should indicate unit examples

Keywords:
Status:	CLOSED CURRENTRELEASE
Alias:	None
Product:	OpenShift Container Platform
Classification:	Red Hat
Component:	Documentation
Sub Component:
Version:	3.1.0
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Target Release:	---
Assignee:	Vikram Goyal
QA Contact:	Vikram Goyal
Docs Contact:	Vikram Goyal
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2016-03-18 23:35 UTC by Erik M Jacobs
Modified:	2017-12-29 22:17 UTC (History)
CC List:	3 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2017-12-29 22:17:29 UTC
Target Upstream Version:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.

Note You need to log in before you can comment on or make changes to this bug.