openshift/openshift-docs
1
0
Fork 0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Code Issues Releases Activity

Correct Elasticsearch naming

Browse Source
This commit is contained in:
Cody Hoag
2019-11-06 21:21:20 -05:00
parent 9482ddccea
commit a85faf4bd7
6 changed files with 14 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
logging/dedicated-cluster-logging.adoc
View File

@@ -6,7 +6,7 @@ include::modules/common-attributes.adoc[]
As an {product-title} cluster administrator, you can deploy cluster logging
to aggregate logs for a range of services.
{product-title} clusters can perform logging tasks using the ElasticSearch
{product-title} clusters can perform logging tasks using the Elasticsearch
Operator. Cluster logging is configured through the Curator tool to retain logs
for two days.

2
machine_management/creating-infrastructure-machinesets.adoc
View File

@@ -25,7 +25,7 @@ include::modules/infrastructure-components.adoc[leveloffset=+1]
In a production deployment, deploy at least three MachineSets to hold
infrastructure components. Both the logging aggregation solution and
the service mesh deploy ElasticSearch, and ElasticSearch requires three
the service mesh deploy Elasticsearch, and Elasticsearch requires three
instances that are installed on different nodes. For high availability, install
deploy these nodes to different availability zones. Since you need different
MachineSets for each availability zone, create at least three MachineSets.

10
modules/nodes-cluster-overcommit-resource-requests.adoc
View File

@@ -70,8 +70,8 @@ The value of `buffer_queue_limit` will be `32`. To change the `buffer_queue_limi
In this formula, `number_of_outputs` is `1` if all the logs are sent to a single resource, and it is incremented by `1` for each additional resource. For example, the value of `number_of_outputs` is:
* `1` - if all logs are sent to a single ElasticSearch pod
* `2` - if application logs are sent to an ElasticSearch pod and ops logs are sent to
another ElasticSearch pod
* `4` - if application logs are sent to an ElasticSearch pod, ops logs are sent to
another ElasticSearch pod, and both of them are forwarded to other Fluentd instances
* `1` - if all logs are sent to a single Elasticsearch pod
* `2` - if application logs are sent to an Elasticsearch pod and ops logs are sent to
another Elasticsearch pod
* `4` - if application logs are sent to an Elasticsearch pod, ops logs are sent to
another Elasticsearch pod, and both of them are forwarded to other Fluentd instances

4
modules/recommended-configurable-storage-technology.adoc
View File

@@ -65,7 +65,7 @@ A scaled registry is an {product-title} registry where three or more pod replica
====
Testing shows issues with using the NFS server on RHEL as storage backend for
the container image registry. This includes the OpenShift Container Registry and Quay, Cassandra
for metrics storage, and ElasticSearch for logging storage. Therefore, using NFS
for metrics storage, and Elasticsearch for logging storage. Therefore, using NFS
to back PVs used by core services is not recommended.
Other NFS implementations on the marketplace might not have these issues.
@@ -118,7 +118,7 @@ In an {product-title} hosted logging cluster deployment:
[IMPORTANT]
====
Testing shows issues with using the NFS server on RHEL as storage backend for
the container image registry. This includes ElasticSearch for logging storage.
the container image registry. This includes Elasticsearch for logging storage.
Therefore, using NFS to back PVs used by core services is not recommended.
Other NFS implementations on the marketplace might not have these issues.

8
release_notes/ocp-4-1-release-notes.adoc
View File

@@ -798,12 +798,12 @@ will fail and may require a username and password challenge if enabled.
`ServiceAccountTokenVolumeProjection` is used.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1695196[*BZ#1695196*])
* The `es nodeCount` in ElasticSearch CRD instances can not be scaled up if
* The `es nodeCount` in Elasticsearch CRD instances can not be scaled up if
deployed with three nodes. Scaling works correctly if deployed with one, two,
four, five or six ElasticSearch CRD instances.
four, five or six Elasticsearch CRD instances.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1712955[*BZ#1712955*])
* ElasticSearch instances created from OperatorHub deploy with a one CPU limit,
* Elasticsearch instances created from OperatorHub deploy with a one CPU limit,
even though no limits are specified.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1710657[*BZ#1710657*])
@@ -853,7 +853,7 @@ deployed due a pod stuck in a `Pending` status.
Broadwell CPU model 79 (type m4) because the `microcode_ctl` will not update.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1710981[*BZ#1710981*])
* New ElasticSearch deployments can not be created if another ElasticSearch
* New Elasticsearch deployments can not be created if another Elasticsearch
deployment is stuck in a deleting state.
(link:https://bugzilla.redhat.com/show_bug.cgi?id=1711044[*BZ#1711044*])

2
welcome/oce_about.adoc
View File

@@ -160,7 +160,7 @@ the kubevirt.io open source project.
=== Advanced cluster management
A {oce} subscription does not offer a cluster-wide log aggregation
solution or support ElasticSearch, Fluentd, Kibana based logging solutions.
solution or support Elasticsearch, Fluentd, Kibana based logging solutions.
Similarly the chargeback features found in {product-title} and Red Hat Service
Mesh capabilities derived from the open source Istio.io and kiali.io projects
that offers OpenTracing observability for containerized services on