kubernetes/aai/components/aai-elasticsearch/resources/config/elasticsearch.yml - onap/oom - Gitiles

 {{/*
 # Copyright © 2018 Amdocs, Bell Canada, AT&T
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
 # You may obtain a copy of the License at
 #
 #       http://www.apache.org/licenses/LICENSE-2.0
 #
 # Unless required by applicable law or agreed to in writing, software
 # distributed under the License is distributed on an "AS IS" BASIS,
 # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 # See the License for the specific language governing permissions and
 # limitations under the License.


 ##################### Elasticsearch Configuration Example #####################

 # This file contains an overview of various configuration settings,
 # targeted at operations staff. Application developers should
 # consult the guide at <http://elasticsearch.org/guide>.
 #
 # The installation procedure is covered at
 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>.
 #
 # Elasticsearch comes with reasonable defaults for most settings,
 # so you can try it out without bothering with configuration.
 #
 # Most of the time, these defaults are just fine for running a production
 # cluster. If you're fine-tuning your cluster, or wondering about the
 # effect of certain configuration option, please _do ask_ on the
 # mailing list or IRC channel [http://elasticsearch.org/community].

 # Any element in the configuration can be replaced with environment variables
 # by placing them in ${...} notation. For example:
 #
 # node.rack: ${RACK_ENV_VAR}

 # For information on supported formats and syntax for the config file, see
 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html>
 ################################### Cluster ###################################

 # Cluster name identifies your cluster for auto-discovery. If you're running
 # multiple clusters on the same network, make sure you're using unique names.
 #
 # cluster.name: elasticsearch
 */}}
 cluster.name: ES_AAI

 #################################### Node #####################################

 node.name: ES_ONAP
 node.master: true
 node.data: true

 {{/*
 # Use the Cluster Health API [http://localhost:9200/_cluster/health], the
 # Node Info API [http://localhost:9200/_nodes] or GUI tools
 # such as <http://www.elasticsearch.org/overview/marvel/>,
 # <http://github.com/karmi/elasticsearch-paramedic>,
 # <http://github.com/lukas-vlcek/bigdesk> and
 # <http://mobz.github.com/elasticsearch-head> to inspect the cluster state.

 # By default, multiple nodes are allowed to start from the same installation location
 # to disable it, set the following:
 */}}
 node.max_local_storage_nodes: 1

 {{/*
 #################################### Index ####################################
 # You can set a number of options (such as shard/replica options, mapping
 # or analyzer definitions, translog settings, ...) for indices globally,
 # in this file.
 #
 # Note, that it makes more sense to configure index settings specifically for
 # a certain index, either when creating it or by using the index templates API.
 #
 # See <http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html> and
 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html>
 # for more information.

 # Set the number of shards (splits) of an index (5 by default):

 #index.number_of_shards: 5

 # Set the number of replicas (additional copies) of an index (1 by default):

 #index.number_of_replicas: 1

 # These settings directly affect the performance of index and search operations
 # in your cluster. Assuming you have enough machines to hold shards and
 # replicas, the rule of thumb is:
 #
 # 1. Having more *shards* enhances the _indexing_ performance and allows to
 #    _distribute_ a big index across machines.
 # 2. Having more *replicas* enhances the _search_ performance and improves the
 #    cluster _availability_.
 #
 # The "number_of_shards" is a one-time setting for an index.
 #
 # The "number_of_replicas" can be increased or decreased anytime,
 # by using the Index Update Settings API.
 #
 # Elasticsearch takes care about load balancing, relocating, gathering the
 # results from nodes, etc. Experiment with different settings to fine-tune
 # your setup.

 # Use the Index Status API (<http://localhost:9200/A/_status>) to inspect
 # the index status.


 #################################### Paths ####################################

 # Path to directory containing configuration (this file and logging.yml):
 #path.conf: /opt/app/elasticsearch/config

 # Path to directory where to store index data allocated for this node.
 # Use swm auto link to redirect the data directory if necessary.
 */}}
 path.data: /usr/share/elasticsearch/data

 # path.data: /path/to/data1,/path/to/data2

 # path.work: /path/to/work

 path.logs: /usr/share/elasticsearch/logs

 #path.plugins: /opt/app/elasticsearch/plugins

 {{/*
 #################################### Plugin ###################################

 # If a plugin listed here is not installed for current node, the node will not start.
 #
 # plugin.mandatory: mapper-attachments,lang-groovy


 ################################### Memory ####################################

 # Elasticsearch performs poorly when JVM starts swapping: you should ensure that
 # it _never_ swaps.
 #
 # Set this property to true to lock the memory: default is true

 #bootstrap.memory_lock: true

 # Make sure that the ES_MIN_MEM and ES_MAX_MEM environment variables are set
 # to the same value, and that the machine has enough memory to allocate
 # for Elasticsearch, leaving enough memory for the operating system itself.
 #
 # You should also make sure that the Elasticsearch process is allowed to lock
 # the memory, eg. by using `ulimit -l unlimited`.

 ### Kernel Settings

 # Elasticsearch installs system call filters of various flavors depending on the
 # operating system (e.g., seccomp on Linux). These system call filters are
 # installed to prevent the ability to execute system calls related to forking
 # as a defense mechanism against arbitrary code execution attacks on
 # Elasticsearch The system call filter check ensures that if system call
 # filters are enabled, then they were successfully installed. To pass the system
 # call filter check you must either fix any configuration errors on your system
 # that prevented system call filters from installing (check your logs), or at
 # your own risk disable system call filters by setting
 # bootstrap.system_call_filter to false.
 # See: https://www.elastic.co/guide/en/elasticsearch/reference/current/system-call-filter-check.html
 #
 # seccomp is found in Linux kernels: 2.6.37�2.6.39, 3.0�3.19, 4.0�4.9,
 # 4.10-rc+HEAD
 #
 # The default setting is to disable the filters assuming an older kernel
 # version where seccomp is not available.
 # See: https://discuss.elastic.co/t/elasticsearch-warn-unable-to-install-syscall-filter/42819
 */}}
 bootstrap.system_call_filter: false

 {{/*
 ############################## Network And HTTP ###############################
 # Elasticsearch, by default, binds itself to the 0.0.0.0 address, and listens
 # on port [9200-9300] for HTTP traffic and on port [9300-9400] for node-to-node
 # communication. (the range means that if the port is busy, it will automatically
 # try the next port).

 # Set the bind address specifically (IPv4 or IPv6):
 */}}
 network.bind_host: 0.0.0.0

 {{/*
 # Set the address other nodes will use to communicate with this node. If not
 # set, it is automatically derived. It must point to an actual IP address.

 # network.publish_host: 0.0.0.0

 # Set both 'bind_host' and 'publish_host':
 # network.host: 192.168.0.1


 # Set a custom port for the node to node communication (9300 by default):
 */}}
 transport.tcp.port: {{ .Values.service.internalPort2 }}

 # Enable compression for all communication between nodes (disabled by default):
 transport.tcp.compress: false

 # Set a custom port to listen for HTTP traffic:
 # http.port: 9200
 http.port: {{ .Values.service.internalPort }}

 # Set a custom allowed content length:
 # http.max_content_length: 100mb
 http.max_content_length: 100mb

 # Disable HTTP completely:
 # http.enabled: false
 http.enabled: true

 # This is specifically useful for permitting which front end Kibana Url's are permitted to access elastic search.
 http.cors.enabled: false
 http.cors.allow-origin: "/.*/"
 http.cors.allow-headers: X-Requested-With, Content-Type, Content-Length
 http.cors.allow-credentials: false
 {{/*
 ################################### Gateway ###################################

 # The gateway allows for persisting the cluster state between full cluster
 # restarts. Every change to the state (such as adding an index) will be stored
 # in the gateway, and when the cluster starts up for the first time,
 # it will read its state from the gateway.
 # There are several types of gateway implementations. For more information, see
 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html>.

 # The default gateway type is the "local" gateway (recommended):
 #
 #gateway.type: local
 #gateway.type: local

 # Settings below control how and when to start the initial recovery process on
 # a full cluster restart (to reuse as much local data as possible when using shared
 # gateway).

 # Allow recovery process after N nodes in a cluster are up:
 #
 # gateway.recover_after_nodes: 1
 */}}
 gateway.recover_after_nodes: 1

 # Set the timeout to initiate the recovery process, once the N nodes
 # from previous setting are up (accepts time value):
 #
 #gateway.recover_after_time: 5m
 gateway.recover_after_time: 5m

 # Set how many nodes are expected in this cluster. Once these N nodes
 # are up (and recover_after_nodes is met), begin recovery process immediately
 # (without waiting for recover_after_time to expire):
 #
 # gateway.expected_nodes: 2
 gateway.expected_nodes: 2

 {{/*
 ############################# Recovery Throttling #############################

 # These settings allow to control the process of shards allocation between
 # nodes during initial recovery, replica allocation, rebalancing,
 # or when adding and removing nodes.

 # Set the number of concurrent recoveries happening on a node:
 #
 # 1. During the initial recovery
 #
 # cluster.routing.allocation.node_initial_primaries_recoveries: 4
 #
 # 2. During adding/removing nodes, rebalancing, etc
 #
 # cluster.routing.allocation.node_concurrent_recoveries: 2

 # Set to throttle throughput when recovering (eg. 100mb, by default 20mb):
 # indices.recovery.max_bytes_per_sec: 20mb
 */}}
 indices.recovery.max_bytes_per_sec: 20mb

 {{/*
 # Set to limit the number of open concurrent streams when
 # recovering a shard from a peer:
 #
 # indices.recovery.concurrent_streams: 5
 #indices.recovery.concurrent_streams: 5

 ################################## Discovery ##################################

 # Discovery infrastructure ensures nodes can be found within a cluster
 # and master node is elected. Multicast discovery is the default.

 # Set to ensure a node sees N other master eligible nodes to be considered
 # operational within the cluster. Its recommended to set it to a higher value
 # than 1 when running more than 2 nodes in the cluster.
 #
 */}}
 discovery.zen.minimum_master_nodes: 1

 {{/*
 # Set the time to wait for ping responses from other nodes when discovering.
 # Set this option to a higher value on a slow or congested network
 # to minimize discovery failures:
 #
 # discovery.zen.ping_timeout: 3s
 */}}
 discovery.zen.ping_timeout: 3s

 {{/*
 # For more information, see
 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html>

 # Unicast discovery allows to explicitly control which nodes will be used
 # to discover the cluster. It can be used when multicast is not present,
 # or to restrict the cluster communication-wise.
 #
 # 1. Disable multicast discovery (enabled by default):
 # discovery.zen.ping.multicast.enabled: false
 #discovery.zen.ping.multicast.enabled: false


 # 2. Configure an initial list of master nodes in the cluster
 #    to perform discovery when new nodes (master or data) are started:
 #
 # discovery.zen.ping.unicast.hosts: ["host1", "host2:port"]

 */}}
 discovery.zen.ping.unicast.hosts: ["0.0.0.0"]

 {{/*
 # EC2 discovery allows to use AWS EC2 API in order to perform discovery.
 #
 # You have to install the cloud-aws plugin for enabling the EC2 discovery.
 #
 # For more information, see
 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html>
 #
 #
 # See <http://elasticsearch.org/tutorials/elasticsearch-on-ec2/>
 # for a step-by-step tutorial.

 # GCE discovery allows to use Google Compute Engine API in order to perform discovery.
 #
 # You have to install the cloud-gce plugin for enabling the GCE discovery.
 #
 # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-gce>.

 # Azure discovery allows to use Azure API in order to perform discovery.
 #
 # You have to install the cloud-azure plugin for enabling the Azure discovery.
 #
 # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-azure>.

 ################################## Slow Log ##################################

 # Shard level query and fetch threshold logging.

 #index.search.slowlog.threshold.query.warn: 10s
 #index.search.slowlog.threshold.query.info: 5s
 #index.search.slowlog.threshold.query.debug: 2s
 #index.search.slowlog.threshold.query.trace: 500ms

 #index.search.slowlog.threshold.fetch.warn: 1s
 #index.search.slowlog.threshold.fetch.info: 800ms
 #index.search.slowlog.threshold.fetch.debug: 500ms
 #index.search.slowlog.threshold.fetch.trace: 200ms

 #index.indexing.slowlog.threshold.index.warn: 10s
 #index.indexing.slowlog.threshold.index.info: 5s
 #index.indexing.slowlog.threshold.index.debug: 2s
 #index.indexing.slowlog.threshold.index.trace: 500ms

 ################################## GC Logging ################################

 #monitor.jvm.gc.young.warn: 1000ms
 #monitor.jvm.gc.young.info: 700ms
 #monitor.jvm.gc.young.debug: 400ms

 #monitor.jvm.gc.old.warn: 10s
 #monitor.jvm.gc.old.info: 5s
 #monitor.jvm.gc.old.debug: 2s


 # x-pack security conflicts with searchguard
 */}}
 xpack.security.enabled: false
 xpack.ml.enabled: false
 xpack.monitoring.enabled: false
 xpack.watcher.enabled: false
	{{/*
	# Copyright © 2018 Amdocs, Bell Canada, AT&T
	#
	# Licensed under the Apache License, Version 2.0 (the "License");
	# you may not use this file except in compliance with the License.
	# You may obtain a copy of the License at
	#
	# http://www.apache.org/licenses/LICENSE-2.0
	#
	# Unless required by applicable law or agreed to in writing, software
	# distributed under the License is distributed on an "AS IS" BASIS,
	# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
	# See the License for the specific language governing permissions and
	# limitations under the License.


	##################### Elasticsearch Configuration Example #####################

	# This file contains an overview of various configuration settings,
	# targeted at operations staff. Application developers should
	# consult the guide at <http://elasticsearch.org/guide>.
	#
	# The installation procedure is covered at
	# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>.
	#
	# Elasticsearch comes with reasonable defaults for most settings,
	# so you can try it out without bothering with configuration.
	#
	# Most of the time, these defaults are just fine for running a production
	# cluster. If you're fine-tuning your cluster, or wondering about the
	# effect of certain configuration option, please _do ask_ on the
	# mailing list or IRC channel [http://elasticsearch.org/community].

	# Any element in the configuration can be replaced with environment variables
	# by placing them in ${...} notation. For example:
	#
	# node.rack: ${RACK_ENV_VAR}

	# For information on supported formats and syntax for the config file, see
	# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html>
	################################### Cluster ###################################

	# Cluster name identifies your cluster for auto-discovery. If you're running
	# multiple clusters on the same network, make sure you're using unique names.
	#
	# cluster.name: elasticsearch
	*/}}
	cluster.name: ES_AAI

	#################################### Node #####################################

	node.name: ES_ONAP
	node.master: true
	node.data: true

	{{/*
	# Use the Cluster Health API [http://localhost:9200/_cluster/health], the
	# Node Info API [http://localhost:9200/_nodes] or GUI tools
	# such as <http://www.elasticsearch.org/overview/marvel/>,
	# <http://github.com/karmi/elasticsearch-paramedic>,
	# <http://github.com/lukas-vlcek/bigdesk> and
	# <http://mobz.github.com/elasticsearch-head> to inspect the cluster state.

	# By default, multiple nodes are allowed to start from the same installation location
	# to disable it, set the following:
	*/}}
	node.max_local_storage_nodes: 1

	{{/*
	#################################### Index ####################################
	# You can set a number of options (such as shard/replica options, mapping
	# or analyzer definitions, translog settings, ...) for indices globally,
	# in this file.
	#
	# Note, that it makes more sense to configure index settings specifically for
	# a certain index, either when creating it or by using the index templates API.
	#
	# See <http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html> and
	# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html>
	# for more information.

	# Set the number of shards (splits) of an index (5 by default):

	#index.number_of_shards: 5

	# Set the number of replicas (additional copies) of an index (1 by default):

	#index.number_of_replicas: 1

	# These settings directly affect the performance of index and search operations
	# in your cluster. Assuming you have enough machines to hold shards and
	# replicas, the rule of thumb is:
	#
	# 1. Having more shards enhances the _indexing_ performance and allows to
	# _distribute_ a big index across machines.
	# 2. Having more replicas enhances the _search_ performance and improves the
	# cluster _availability_.
	#
	# The "number_of_shards" is a one-time setting for an index.
	#
	# The "number_of_replicas" can be increased or decreased anytime,
	# by using the Index Update Settings API.
	#
	# Elasticsearch takes care about load balancing, relocating, gathering the
	# results from nodes, etc. Experiment with different settings to fine-tune
	# your setup.

	# Use the Index Status API (<http://localhost:9200/A/_status>) to inspect
	# the index status.


	#################################### Paths ####################################

	# Path to directory containing configuration (this file and logging.yml):
	#path.conf: /opt/app/elasticsearch/config

	# Path to directory where to store index data allocated for this node.
	# Use swm auto link to redirect the data directory if necessary.
	*/}}
	path.data: /usr/share/elasticsearch/data

	# path.data: /path/to/data1,/path/to/data2

	# path.work: /path/to/work

	path.logs: /usr/share/elasticsearch/logs

	#path.plugins: /opt/app/elasticsearch/plugins

	{{/*
	#################################### Plugin ###################################

	# If a plugin listed here is not installed for current node, the node will not start.
	#
	# plugin.mandatory: mapper-attachments,lang-groovy


	################################### Memory ####################################

	# Elasticsearch performs poorly when JVM starts swapping: you should ensure that
	# it _never_ swaps.
	#
	# Set this property to true to lock the memory: default is true

	#bootstrap.memory_lock: true

	# Make sure that the ES_MIN_MEM and ES_MAX_MEM environment variables are set
	# to the same value, and that the machine has enough memory to allocate
	# for Elasticsearch, leaving enough memory for the operating system itself.
	#
	# You should also make sure that the Elasticsearch process is allowed to lock
	# the memory, eg. by using `ulimit -l unlimited`.

	### Kernel Settings

	# Elasticsearch installs system call filters of various flavors depending on the
	# operating system (e.g., seccomp on Linux). These system call filters are
	# installed to prevent the ability to execute system calls related to forking
	# as a defense mechanism against arbitrary code execution attacks on
	# Elasticsearch The system call filter check ensures that if system call
	# filters are enabled, then they were successfully installed. To pass the system
	# call filter check you must either fix any configuration errors on your system
	# that prevented system call filters from installing (check your logs), or at
	# your own risk disable system call filters by setting
	# bootstrap.system_call_filter to false.
	# See: https://www.elastic.co/guide/en/elasticsearch/reference/current/system-call-filter-check.html
	#
	# seccomp is found in Linux kernels: 2.6.37�2.6.39, 3.0�3.19, 4.0�4.9,
	# 4.10-rc+HEAD
	#
	# The default setting is to disable the filters assuming an older kernel
	# version where seccomp is not available.
	# See: https://discuss.elastic.co/t/elasticsearch-warn-unable-to-install-syscall-filter/42819
	*/}}
	bootstrap.system_call_filter: false

	{{/*
	############################## Network And HTTP ###############################
	# Elasticsearch, by default, binds itself to the 0.0.0.0 address, and listens
	# on port [9200-9300] for HTTP traffic and on port [9300-9400] for node-to-node
	# communication. (the range means that if the port is busy, it will automatically
	# try the next port).

	# Set the bind address specifically (IPv4 or IPv6):
	*/}}
	network.bind_host: 0.0.0.0

	{{/*
	# Set the address other nodes will use to communicate with this node. If not
	# set, it is automatically derived. It must point to an actual IP address.

	# network.publish_host: 0.0.0.0

	# Set both 'bind_host' and 'publish_host':
	# network.host: 192.168.0.1


	# Set a custom port for the node to node communication (9300 by default):
	*/}}
	transport.tcp.port: {{ .Values.service.internalPort2 }}

	# Enable compression for all communication between nodes (disabled by default):
	transport.tcp.compress: false

	# Set a custom port to listen for HTTP traffic:
	# http.port: 9200
	http.port: {{ .Values.service.internalPort }}

	# Set a custom allowed content length:
	# http.max_content_length: 100mb
	http.max_content_length: 100mb

	# Disable HTTP completely:
	# http.enabled: false
	http.enabled: true

	# This is specifically useful for permitting which front end Kibana Url's are permitted to access elastic search.
	http.cors.enabled: false
	http.cors.allow-origin: "/.*/"
	http.cors.allow-headers: X-Requested-With, Content-Type, Content-Length
	http.cors.allow-credentials: false
	{{/*
	################################### Gateway ###################################

	# The gateway allows for persisting the cluster state between full cluster
	# restarts. Every change to the state (such as adding an index) will be stored
	# in the gateway, and when the cluster starts up for the first time,
	# it will read its state from the gateway.
	# There are several types of gateway implementations. For more information, see
	# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html>.

	# The default gateway type is the "local" gateway (recommended):
	#
	#gateway.type: local
	#gateway.type: local

	# Settings below control how and when to start the initial recovery process on
	# a full cluster restart (to reuse as much local data as possible when using shared
	# gateway).

	# Allow recovery process after N nodes in a cluster are up:
	#
	# gateway.recover_after_nodes: 1
	*/}}
	gateway.recover_after_nodes: 1

	# Set the timeout to initiate the recovery process, once the N nodes
	# from previous setting are up (accepts time value):
	#
	#gateway.recover_after_time: 5m
	gateway.recover_after_time: 5m

	# Set how many nodes are expected in this cluster. Once these N nodes
	# are up (and recover_after_nodes is met), begin recovery process immediately
	# (without waiting for recover_after_time to expire):
	#
	# gateway.expected_nodes: 2
	gateway.expected_nodes: 2

	{{/*
	############################# Recovery Throttling #############################

	# These settings allow to control the process of shards allocation between
	# nodes during initial recovery, replica allocation, rebalancing,
	# or when adding and removing nodes.

	# Set the number of concurrent recoveries happening on a node:
	#
	# 1. During the initial recovery
	#
	# cluster.routing.allocation.node_initial_primaries_recoveries: 4
	#
	# 2. During adding/removing nodes, rebalancing, etc
	#
	# cluster.routing.allocation.node_concurrent_recoveries: 2

	# Set to throttle throughput when recovering (eg. 100mb, by default 20mb):
	# indices.recovery.max_bytes_per_sec: 20mb
	*/}}
	indices.recovery.max_bytes_per_sec: 20mb

	{{/*
	# Set to limit the number of open concurrent streams when
	# recovering a shard from a peer:
	#
	# indices.recovery.concurrent_streams: 5
	#indices.recovery.concurrent_streams: 5

	################################## Discovery ##################################

	# Discovery infrastructure ensures nodes can be found within a cluster
	# and master node is elected. Multicast discovery is the default.

	# Set to ensure a node sees N other master eligible nodes to be considered
	# operational within the cluster. Its recommended to set it to a higher value
	# than 1 when running more than 2 nodes in the cluster.
	#
	*/}}
	discovery.zen.minimum_master_nodes: 1

	{{/*
	# Set the time to wait for ping responses from other nodes when discovering.
	# Set this option to a higher value on a slow or congested network
	# to minimize discovery failures:
	#
	# discovery.zen.ping_timeout: 3s
	*/}}
	discovery.zen.ping_timeout: 3s

	{{/*
	# For more information, see
	# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html>

	# Unicast discovery allows to explicitly control which nodes will be used
	# to discover the cluster. It can be used when multicast is not present,
	# or to restrict the cluster communication-wise.
	#
	# 1. Disable multicast discovery (enabled by default):
	# discovery.zen.ping.multicast.enabled: false
	#discovery.zen.ping.multicast.enabled: false


	# 2. Configure an initial list of master nodes in the cluster
	# to perform discovery when new nodes (master or data) are started:
	#
	# discovery.zen.ping.unicast.hosts: ["host1", "host2:port"]

	*/}}
	discovery.zen.ping.unicast.hosts: ["0.0.0.0"]

	{{/*
	# EC2 discovery allows to use AWS EC2 API in order to perform discovery.
	#
	# You have to install the cloud-aws plugin for enabling the EC2 discovery.
	#
	# For more information, see
	# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html>
	#
	#
	# See <http://elasticsearch.org/tutorials/elasticsearch-on-ec2/>
	# for a step-by-step tutorial.

	# GCE discovery allows to use Google Compute Engine API in order to perform discovery.
	#
	# You have to install the cloud-gce plugin for enabling the GCE discovery.
	#
	# For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-gce>.

	# Azure discovery allows to use Azure API in order to perform discovery.
	#
	# You have to install the cloud-azure plugin for enabling the Azure discovery.
	#
	# For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-azure>.

	################################## Slow Log ##################################

	# Shard level query and fetch threshold logging.

	#index.search.slowlog.threshold.query.warn: 10s
	#index.search.slowlog.threshold.query.info: 5s
	#index.search.slowlog.threshold.query.debug: 2s
	#index.search.slowlog.threshold.query.trace: 500ms

	#index.search.slowlog.threshold.fetch.warn: 1s
	#index.search.slowlog.threshold.fetch.info: 800ms
	#index.search.slowlog.threshold.fetch.debug: 500ms
	#index.search.slowlog.threshold.fetch.trace: 200ms

	#index.indexing.slowlog.threshold.index.warn: 10s
	#index.indexing.slowlog.threshold.index.info: 5s
	#index.indexing.slowlog.threshold.index.debug: 2s
	#index.indexing.slowlog.threshold.index.trace: 500ms

	################################## GC Logging ################################

	#monitor.jvm.gc.young.warn: 1000ms
	#monitor.jvm.gc.young.info: 700ms
	#monitor.jvm.gc.young.debug: 400ms

	#monitor.jvm.gc.old.warn: 10s
	#monitor.jvm.gc.old.info: 5s
	#monitor.jvm.gc.old.debug: 2s


	# x-pack security conflicts with searchguard
	*/}}
	xpack.security.enabled: false
	xpack.ml.enabled: false
	xpack.monitoring.enabled: false
	xpack.watcher.enabled: false