Fix typo elasticserch to elasticsearch
Change-Id: I3e31373be3af65c8a2b54ad32c8ea24c72ab5a41
This commit is contained in:
parent
a4181c96ae
commit
8388a54f52
@ -97,7 +97,7 @@ _elasticsearch_discovery_seed_hosts: >-
|
|||||||
| default((groups['elastic'] | union(groups['kibana'])) | map('extract', hostvars, 'ansible_host') | list)
|
| default((groups['elastic'] | union(groups['kibana'])) | map('extract', hostvars, 'ansible_host') | list)
|
||||||
}}
|
}}
|
||||||
|
|
||||||
elasticserch_interface_speed: |-
|
elasticsearch_interface_speed: |-
|
||||||
{% set default_interface_fact = hostvars[inventory_hostname]['ansible_' + (elastic_data_interface | replace('-', '_'))] %}
|
{% set default_interface_fact = hostvars[inventory_hostname]['ansible_' + (elastic_data_interface | replace('-', '_'))] %}
|
||||||
{% set speeds = [] %}
|
{% set speeds = [] %}
|
||||||
{% if default_interface_fact['type'] == 'bridge' %}
|
{% if default_interface_fact['type'] == 'bridge' %}
|
||||||
|
@ -155,7 +155,7 @@ indices.memory.index_buffer_size: 20%
|
|||||||
# Connection throttling on recovery is limited to 20% of the detected interface
|
# Connection throttling on recovery is limited to 20% of the detected interface
|
||||||
# speed with a cap of 750mb. This will improce search speeds and reduce general
|
# speed with a cap of 750mb. This will improce search speeds and reduce general
|
||||||
# cluster pressure.
|
# cluster pressure.
|
||||||
indices.recovery.max_bytes_per_sec: {{ elasticserch_interface_speed }}mb
|
indices.recovery.max_bytes_per_sec: {{ elasticsearch_interface_speed }}mb
|
||||||
|
|
||||||
# ---------------------------------- X-Pack ------------------------------------
|
# ---------------------------------- X-Pack ------------------------------------
|
||||||
# X-Pack Monitoring
|
# X-Pack Monitoring
|
||||||
|
@ -26,7 +26,7 @@
|
|||||||
|
|
||||||
tasks:
|
tasks:
|
||||||
|
|
||||||
# the elasticserch cluster elects one master from all those which are marked as master-eligible
|
# the elasticsearch cluster elects one master from all those which are marked as master-eligible
|
||||||
# 1 node cluster can only have one master
|
# 1 node cluster can only have one master
|
||||||
# 2 node clusters have 1 master-eligable nodes to avoid split-brain
|
# 2 node clusters have 1 master-eligable nodes to avoid split-brain
|
||||||
# 3 node clusters have 3 master-eligable nodes
|
# 3 node clusters have 3 master-eligable nodes
|
||||||
|
Loading…
x
Reference in New Issue
Block a user