Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BZ1731358 Added valid time units, fixed typo. #20885

Merged
merged 1 commit into from
Apr 15, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 5 additions & 9 deletions install_config/aggregate_logging.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -493,7 +493,7 @@ When `openshift_logging_es_pvc_prefix` is set, and:
* `openshift_logging_es_pvc_dynamic`=`false`, the value for `openshift_logging_es_pvc_size` must be set.

|`openshift_logging_es_recover_after_time`
|The amount of time Elasticsearch will wait before it tries to recover.
|The amount of time Elasticsearch will wait before it tries to recover. Supported time units are seconds (s) or minutes (m).

|`openshift_logging_es_storage_group`
|Number of a supplemental group ID for access to Elasticsearch storage volumes.
Expand Down Expand Up @@ -554,10 +554,6 @@ when `openshift_logging_use_ops` is set to `true`.
|Equivalent to `openshift_logging_es_pvc_prefix` for Ops cluster
when `openshift_logging_use_ops` is set to `true`.

|`openshift_logging_es_ops_recover_after_time`
|Equivalent to `openshift_logging_es_recovery_after_time` for Ops cluster
when `openshift_logging_use_ops` is set to `true`.

|`openshift_logging_es_ops_storage_group`
|Equivalent to `openshift_logging_es_storage_group` for Ops cluster
when `openshift_logging_use_ops` is set to `true`.
Expand Down Expand Up @@ -1232,11 +1228,11 @@ of Elasticsearch nodes (scaled up) in the cluster.
You can change the number of Elasticsearch replicas by editing the `openshift_logging_es_number_of_replicas` value
in the inventory host file and re-running the logging playbook as described previously.

The changes apply only to the new indices. Existing indices continue to use the previous number of replicas.
For example, if you change the number of indices from 3 to 2, your cluster will use 2 replicas for new indices
and 3 replicas for existing indices.
The changes apply only to the new indices. Existing indices continue to use the previous number of replicas.
For example, if you change the number of indices from 3 to 2, your cluster will use 2 replicas for new indices
and 3 replicas for existing indices.

You can modify the replica count for the existing indices by running the following command:
You can modify the replica count for the existing indices by running the following command:

----
$ oc exec -c elasticsearch $pod -- es_util --query=project.* -d '{"index":{"number_of_replicas":"2"}}' <1>
Expand Down