1 {%- from "elasticsearch/map.jinja" import server with context %}
3 ##################### Elasticsearch Configuration Example #####################
5 # This file contains an overview of various configuration settings,
6 # targeted at operations staff. Application developers should
7 # consult the guide at <http://elasticsearch.org/guide>.
9 # The installation procedure is covered at
10 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>.
12 # Elasticsearch comes with reasonable defaults for most settings,
13 # so you can try it out without bothering with configuration.
15 # Most of the time, these defaults are just fine for running a production
16 # cluster. If you're fine-tuning your cluster, or wondering about the
17 # effect of certain configuration option, please _do ask_ on the
18 # mailing list or IRC channel [http://elasticsearch.org/community].
20 # Any element in the configuration can be replaced with environment variables
21 # by placing them in ${...} notation. For example:
23 # node.rack: ${RACK_ENV_VAR}
25 # For information on supported formats and syntax for the config file, see
26 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html>
29 ################################### Cluster ###################################
31 # Cluster name identifies your cluster for auto-discovery. If you're running
32 # multiple clusters on the same network, make sure you're using unique names.
34 # cluster.name: elasticsearch
35 {%- if server.get('cluster', {}).name is defined %}
36 cluster.name: {{ server.cluster.name }}
38 #################################### Node #####################################
40 # Node names are generated dynamically on startup, so you're relieved
41 # from configuring them manually. You can tie this node to a specific name:
43 # node.name: "Franz Kafka"
44 node.name: {{ server.get('name', '${HOSTNAME}') }}
46 # Every node can be configured to allow or deny being eligible as the master,
47 # and to allow or deny to store the data.
49 # Allow this node to be eligible as a master node (enabled by default):
51 node.master: {{ server.get('master', True)|lower }}
53 # Allow this node to store data (enabled by default):
55 node.data: {{ server.get('data', True)|lower }}
57 # You can exploit these settings to design advanced cluster topologies.
59 # 1. You want this node to never become a master node, only to hold data.
60 # This will be the "workhorse" of your cluster.
65 # 2. You want this node to only serve as a master: to not store any data and
66 # to have free resources. This will be the "coordinator" of your cluster.
71 # 3. You want this node to be neither master nor data node, but
72 # to act as a "search load balancer" (fetching data from nodes,
73 # aggregating results, etc.)
78 # Use the Cluster Health API [http://localhost:9200/_cluster/health], the
79 # Node Info API [http://localhost:9200/_nodes] or GUI tools
80 # such as <http://www.elasticsearch.org/overview/marvel/>,
81 # <http://github.com/karmi/elasticsearch-paramedic>,
82 # <http://github.com/lukas-vlcek/bigdesk> and
83 # <http://mobz.github.com/elasticsearch-head> to inspect the cluster state.
85 # A node can have generic attributes associated with it, which can later be used
86 # for customized shard allocation filtering, or allocation awareness. An attribute
87 # is a simple key value pair, similar to node.key: value, here is an example:
90 {%- if server.rack is defined %}
91 node.rack: {{ server.rack }}
94 # By default, multiple nodes are allowed to start from the same installation location
95 # to disable it, set the following:
96 # node.max_local_storage_nodes: 1
98 {%- if server.get('threadpool', {}).get('bulk', {}).queue_size is defined %}
99 # For bulk operations. Thread pool type is fixed with a size of # of available processors.
100 threadpool.bulk.queue_size: {{ server.threadpool.bulk.queue_size }}
103 #################################### Index ####################################
105 # You can set a number of options (such as shard/replica options, mapping
106 # or analyzer definitions, translog settings, ...) for indices globally,
109 # Note, that it makes more sense to configure index settings specifically for
110 # a certain index, either when creating it or by using the index templates API.
112 # See <http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html> and
113 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html>
114 # for more information.
116 # Set the number of shards (splits) of an index (5 by default):
118 index.number_of_shards: {{ server.get('index', {}).get('shards', 5) }}
120 # Set the number of replicas (additional copies) of an index (1 by default):
122 index.number_of_replicas: {{ server.get('index', {}).get('replicas', 1) }}
124 # Note, that for development on a local machine, with small indices, it usually
125 # makes sense to "disable" the distributed features:
127 # index.number_of_shards: 1
128 # index.number_of_replicas: 0
130 # These settings directly affect the performance of index and search operations
131 # in your cluster. Assuming you have enough machines to hold shards and
132 # replicas, the rule of thumb is:
134 # 1. Having more *shards* enhances the _indexing_ performance and allows to
135 # _distribute_ a big index across machines.
136 # 2. Having more *replicas* enhances the _search_ performance and improves the
137 # cluster _availability_.
139 # The "number_of_shards" is a one-time setting for an index.
141 # The "number_of_replicas" can be increased or decreased anytime,
142 # by using the Index Update Settings API.
144 # Elasticsearch takes care about load balancing, relocating, gathering the
145 # results from nodes, etc. Experiment with different settings to fine-tune
148 # Use the Index Status API (<http://localhost:9200/A/_status>) to inspect
152 #################################### Paths ####################################
154 # Path to directory containing configuration (this file and logging.yml):
156 # path.conf: /path/to/conf
158 # Path to directory where to store index data allocated for this node.
160 # path.data: /path/to/data
161 {%- if server.get('path', {}).data is defined %}
162 path.data = {{ server.path.data }}
165 # Can optionally include more than one location, causing data to be striped across
166 # the locations (a la RAID 0) on a file level, favouring locations with most free
167 # space on creation. For example:
169 # path.data: /path/to/data1,/path/to/data2
171 # Path to temporary files:
173 # path.work: /path/to/work
177 # path.logs: /path/to/logs
178 {%- if server.get('path', {}).logs is defined %}
179 path.logs = {{ server.path.logs }}
182 # Path to where plugins are installed:
184 # path.plugins: /path/to/plugins
187 #################################### Plugin ###################################
189 # If a plugin listed here is not installed for current node, the node will not start.
191 # plugin.mandatory: mapper-attachments,lang-groovy
194 ################################### Memory ####################################
196 # Elasticsearch performs poorly when JVM starts swapping: you should ensure that
199 # Set this property to true to lock the memory:
201 # bootstrap.mlockall: true
202 {%- if server.mlockall is defined %}
203 bootstrap.mlockall: {{ server.mlockall|lower }}
206 # Make sure that the ES_MIN_MEM and ES_MAX_MEM environment variables are set
207 # to the same value, and that the machine has enough memory to allocate
208 # for Elasticsearch, leaving enough memory for the operating system itself.
210 # You should also make sure that the Elasticsearch process is allowed to lock
211 # the memory, eg. by using `ulimit -l unlimited`.
214 ############################## Network And HTTP ###############################
216 # Elasticsearch, by default, binds itself to the 0.0.0.0 address, and listens
217 # on port [9200-9300] for HTTP traffic and on port [9300-9400] for node-to-node
218 # communication. (the range means that if the port is busy, it will automatically
219 # try the next port).
221 # Set both 'bind_host' and 'publish_host':
223 # network.host: 192.168.0.1
225 {%- if server.get('bind', {}).address is defined %}
226 network.host: {{ server.bind.address }}
229 # Set specifically the address other nodes will use to communicate with this
230 # node. If not set, it is automatically derived. It must point to an actual
232 {%- if server.publish_host is defined %}
233 network.publish_host: {{ server.publish_host }}
237 # Set a custom port for the node to node communication (9300 by default):
239 # transport.tcp.port: 9300
241 # Enable compression for all communication between nodes (disabled by default):
243 # transport.tcp.compress: true
245 # Set a custom port to listen for HTTP traffic:
248 {%- if server.get('bind', {}).port is defined %}
249 http.port: {{ server.bind.port }}
252 # Set a custom allowed content length:
254 # http.max_content_length: 100mb
256 # Disable HTTP completely:
258 # http.enabled: false
262 ################################### Gateway ###################################
264 # The gateway allows for persisting the cluster state between full cluster
265 # restarts. Every change to the state (such as adding an index) will be stored
266 # in the gateway, and when the cluster starts up for the first time,
267 # it will read its state from the gateway.
269 # There are several types of gateway implementations. For more information, see
270 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html>.
272 # The default gateway type is the "local" gateway (recommended):
274 # gateway.type: local
276 # Settings below control how and when to start the initial recovery process on
277 # a full cluster restart (to reuse as much local data as possible when using shared
280 # Allow recovery process after N nodes in a cluster are up:
282 # gateway.recover_after_nodes: 1
283 {%- if server.get('gateway', {}).recover_after_nodes is defined %}
284 gateway.recover_after_nodes: {{ server.gateway.recover_after_nodes }}
287 # Set the timeout to initiate the recovery process, once the N nodes
288 # from previous setting are up (accepts time value):
290 # gateway.recover_after_time: 5m
291 {%- if server.get('gateway', {}).recover_after_time is defined %}
292 gateway.recover_after_time: {{ server.gateway.recover_after_time }}
295 # Set how many nodes are expected in this cluster. Once these N nodes
296 # are up (and recover_after_nodes is met), begin recovery process immediately
297 # (without waiting for recover_after_time to expire):
299 # gateway.expected_nodes: 2
300 {%- if server.get('gateway', {}).expected_nodes is defined %}
301 gateway.expected_nodes: {{ server.gateway.expected_nodes }}
305 ############################# Recovery Throttling #############################
307 # These settings allow to control the process of shards allocation between
308 # nodes during initial recovery, replica allocation, rebalancing,
309 # or when adding and removing nodes.
311 # Set the number of concurrent recoveries happening on a node:
313 # 1. During the initial recovery
315 # cluster.routing.allocation.node_initial_primaries_recoveries: 4
317 # 2. During adding/removing nodes, rebalancing, etc
319 # cluster.routing.allocation.node_concurrent_recoveries: 2
321 # Set to throttle throughput when recovering (eg. 100mb, by default 20mb):
323 # indices.recovery.max_bytes_per_sec: 20mb
325 # Set to limit the number of open concurrent streams when
326 # recovering a shard from a peer:
328 # indices.recovery.concurrent_streams: 5
331 ################################## Discovery ##################################
333 # Discovery infrastructure ensures nodes can be found within a cluster
334 # and master node is elected. Multicast discovery is the default.
336 # Set to ensure a node sees N other master eligible nodes to be considered
337 # operational within the cluster. Its recommended to set it to a higher value
338 # than 1 when running more than 2 nodes in the cluster.
340 discovery.zen.minimum_master_nodes: {{ server.get('cluster', {}).minimum_master_nodes|default(1) }}
342 # Set the time to wait for ping responses from other nodes when discovering.
343 # Set this option to a higher value on a slow or congested network
344 # to minimize discovery failures:
346 # discovery.zen.ping.timeout: 3s
348 # For more information, see
349 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html>
351 # Unicast discovery allows to explicitly control which nodes will be used
352 # to discover the cluster. It can be used when multicast is not present,
353 # or to restrict the cluster communication-wise.
355 # 1. Disable multicast discovery (enabled by default):
357 discovery.zen.ping.multicast.enabled: {{ server.get('cluster', {}).get('multicast', True)|lower }}
359 # 2. Configure an initial list of master nodes in the cluster
360 # to perform discovery when new nodes (master or data) are started:
362 {%- if server.get('cluster', {}).members is defined %}
363 discovery.zen.ping.unicast.hosts: [{% for member in server.cluster.members %}"{{ member.host }}:{{ member.get('port', 9300) }}"{% if not loop.last %}, {% endif %}{% endfor %}]
366 # EC2 discovery allows to use AWS EC2 API in order to perform discovery.
368 # You have to install the cloud-aws plugin for enabling the EC2 discovery.
370 # For more information, see
371 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html>
373 # See <http://elasticsearch.org/tutorials/elasticsearch-on-ec2/>
374 # for a step-by-step tutorial.
376 # GCE discovery allows to use Google Compute Engine API in order to perform discovery.
378 # You have to install the cloud-gce plugin for enabling the GCE discovery.
380 # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-gce>.
382 # Azure discovery allows to use Azure API in order to perform discovery.
384 # You have to install the cloud-azure plugin for enabling the Azure discovery.
386 # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-azure>.
388 ################################## Slow Log ##################################
390 # Shard level query and fetch threshold logging.
392 #index.search.slowlog.threshold.query.warn: 10s
393 #index.search.slowlog.threshold.query.info: 5s
394 #index.search.slowlog.threshold.query.debug: 2s
395 #index.search.slowlog.threshold.query.trace: 500ms
397 #index.search.slowlog.threshold.fetch.warn: 1s
398 #index.search.slowlog.threshold.fetch.info: 800ms
399 #index.search.slowlog.threshold.fetch.debug: 500ms
400 #index.search.slowlog.threshold.fetch.trace: 200ms
402 #index.indexing.slowlog.threshold.index.warn: 10s
403 #index.indexing.slowlog.threshold.index.info: 5s
404 #index.indexing.slowlog.threshold.index.debug: 2s
405 #index.indexing.slowlog.threshold.index.trace: 500ms
407 ################################## GC Logging ################################
409 #monitor.jvm.gc.young.warn: 1000ms
410 #monitor.jvm.gc.young.info: 700ms
411 #monitor.jvm.gc.young.debug: 400ms
413 #monitor.jvm.gc.old.warn: 10s
414 #monitor.jvm.gc.old.info: 5s
415 #monitor.jvm.gc.old.debug: 2s