blob: b4634c8213449029229c5538b8534d45a47a7742 [file] [log] [blame]
Michael Lando451a3402017-02-19 10:28:42 +02001
2cluster.name: elasticsearch_1_5_2
3
4discovery.zen.ping.unicast.hosts: elasticsearch_host
5
6http.cors.enabled: true
7#plugin.types: "DeleteByQueryPlugin"
8#path.home: "/home/vagrant/catalog-be/config"
9
10elasticSearch.transportclient: true
11
12transport.client.initial_nodes:
13 - elasticsearch_host:9300
14
15##################### Elasticsearch Configuration Example #####################
16
17# This file contains an overview of various configuration settings,
18# targeted at operations staff. Application developers should
19# consult the guide at <http://elasticsearch.org/guide>.
20#
21# The installation procedure is covered at
22# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>.
23#
24# Elasticsearch comes with reasonable defaults for most settings,
25# so you can try it out without bothering with configuration.
26#
27# Most of the time, these defaults are just fine for running a production
28# cluster. If you're fine-tuning your cluster, or wondering about the
29# effect of certain configuration option, please _do ask_ on the
30# mailing list or IRC channel [http://elasticsearch.org/community].
31
32# Any element in the configuration can be replaced with environment variables
33# by placing them in ${...} notation. For example:
34#
35# node.rack: ${RACK_ENV_VAR}
36
37# For information on supported formats and syntax for the config file, see
38# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html>
39
40
41################################### Cluster ###################################
42
43# Cluster name identifies your cluster for auto-discovery. If you're running
44# multiple clusters on the same network, make sure you're using unique names.
45#
46# cluster.name: elasticsearch
47
48
49#################################### Node #####################################
50
51# Node names are generated dynamically on startup, so you're relieved
52# from configuring them manually. You can tie this node to a specific name:
53#
54# node.name: "Franz Kafka"
55
56# Every node can be configured to allow or deny being eligible as the master,
57# and to allow or deny to store the data.
58#
59# Allow this node to be eligible as a master node (enabled by default):
60#
61# node.master: true
62#
63# Allow this node to store data (enabled by default):
64#
65# node.data: true
66
67# You can exploit these settings to design advanced cluster topologies.
68#
69# 1. You want this node to never become a master node, only to hold data.
70# This will be the "workhorse" of your cluster.
71#
72# node.master: false
73# node.data: true
74#
75# 2. You want this node to only serve as a master: to not store any data and
76# to have free resources. This will be the "coordinator" of your cluster.
77#
78# node.master: true
79# node.data: false
80#
81# 3. You want this node to be neither master nor data node, but
82# to act as a "search load balancer" (fetching data from nodes,
83# aggregating results, etc.)
84#
85# node.master: false
86# node.data: false
87
88# Use the Cluster Health API [http://localhost:9200/_cluster/health], the
89# Node Info API [http://localhost:9200/_nodes] or GUI tools
90# such as <http://www.elasticsearch.org/overview/marvel/>,
91# <http://github.com/karmi/elasticsearch-paramedic>,
92# <http://github.com/lukas-vlcek/bigdesk> and
93# <http://mobz.github.com/elasticsearch-head> to inspect the cluster state.
94
95# A node can have generic attributes associated with it, which can later be used
96# for customized shard allocation filtering, or allocation awareness. An attribute
97# is a simple key value pair, similar to node.key: value, here is an example:
98#
99# node.rack: rack314
100
101# By default, multiple nodes are allowed to start from the same installation location
102# to disable it, set the following:
103# node.max_local_storage_nodes: 1
104
105
106#################################### Index ####################################
107
108# You can set a number of options (such as shard/replica options, mapping
109# or analyzer definitions, translog settings, ...) for indices globally,
110# in this file.
111#
112# Note, that it makes more sense to configure index settings specifically for
113# a certain index, either when creating it or by using the index templates API.
114#
115# See <http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html> and
116# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html>
117# for more information.
118
119# Set the number of shards (splits) of an index (5 by default):
120#
121# index.number_of_shards: 5
122
123# Set the number of replicas (additional copies) of an index (1 by default):
124#
125# index.number_of_replicas: 1
126
127# Note, that for development on a local machine, with small indices, it usually
128# makes sense to "disable" the distributed features:
129#
130index.number_of_shards: 1
131index.number_of_replicas: 0
132
133# These settings directly affect the performance of index and search operations
134# in your cluster. Assuming you have enough machines to hold shards and
135# replicas, the rule of thumb is:
136#
137# 1. Having more *shards* enhances the _indexing_ performance and allows to
138# _distribute_ a big index across machines.
139# 2. Having more *replicas* enhances the _search_ performance and improves the
140# cluster _availability_.
141#
142# The "number_of_shards" is a one-time setting for an index.
143#
144# The "number_of_replicas" can be increased or decreased anytime,
145# by using the Index Update Settings API.
146#
147# Elasticsearch takes care about load balancing, relocating, gathering the
148# results from nodes, etc. Experiment with different settings to fine-tune
149# your setup.
150
151# Use the Index Status API (<http://localhost:9200/A/_status>) to inspect
152# the index status.
153
154
155#################################### Paths ####################################
156
157# Path to directory containing configuration (this file and logging.yml):
158#
159path.conf: /src/test/resources
160#path.home: /src/test/resources
161
162# Path to directory where to store index data allocated for this node.
163#
164path.data: target/esdata
165#
166# Can optionally include more than one location, causing data to be striped across
167# the locations (a la RAID 0) on a file level, favouring locations with most free
168# space on creation. For example:
169#
170# path.data: /path/to/data1,/path/to/data2
171
172# Path to temporary files:
173#
174path.work: /target/eswork
175
176# Path to log files:
177#
178path.logs: /target/eslogs
179
180# Path to where plugins are installed:
181#
182# path.plugins: /path/to/plugins
183
184
185#################################### Plugin ###################################
186
187# If a plugin listed here is not installed for current node, the node will not start.
188#
189# plugin.mandatory: mapper-attachments,lang-groovy
190
191
192################################### Memory ####################################
193
194# Elasticsearch performs poorly when JVM starts swapping: you should ensure that
195# it _never_ swaps.
196#
197# Set this property to true to lock the memory:
198#
199# bootstrap.mlockall: true
200
201# Make sure that the ES_MIN_MEM and ES_MAX_MEM environment variables are set
202# to the same value, and that the machine has enough memory to allocate
203# for Elasticsearch, leaving enough memory for the operating system itself.
204#
205# You should also make sure that the Elasticsearch process is allowed to lock
206# the memory, eg. by using `ulimit -l unlimited`.
207
208
209############################## Network And HTTP ###############################
210
211# Elasticsearch, by default, binds itself to the 0.0.0.0 address, and listens
212# on port [9200-9300] for HTTP traffic and on port [9300-9400] for node-to-node
213# communication. (the range means that if the port is busy, it will automatically
214# try the next port).
215
216# Set the bind address specifically (IPv4 or IPv6):
217#
218# network.bind_host: 192.168.0.1
219
220# Set the address other nodes will use to communicate with this node. If not
221# set, it is automatically derived. It must point to an actual IP address.
222#
223# network.publish_host: 192.168.0.1
224
225# Set both 'bind_host' and 'publish_host':
226#
227# network.host: 192.168.0.1
228
229# Set a custom port for the node to node communication (9300 by default):
230#
231# transport.tcp.port: 9300
232
233# Enable compression for all communication between nodes (disabled by default):
234#
235# transport.tcp.compress: true
236
237# Set a custom port to listen for HTTP traffic:
238#
239# http.port: 9200
240
241# Set a custom allowed content length:
242#
243# http.max_content_length: 100mb
244
245# Disable HTTP completely:
246#
247# http.enabled: false
248
249
250################################### Gateway ###################################
251
252# The gateway allows for persisting the cluster state between full cluster
253# restarts. Every change to the state (such as adding an index) will be stored
254# in the gateway, and when the cluster starts up for the first time,
255# it will read its state from the gateway.
256
257# There are several types of gateway implementations. For more information, see
258# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html>.
259
260# The default gateway type is the "local" gateway (recommended):
261#
262# gateway.type: local
263
264# Settings below control how and when to start the initial recovery process on
265# a full cluster restart (to reuse as much local data as possible when using shared
266# gateway).
267
268# Allow recovery process after N nodes in a cluster are up:
269#
270gateway.recover_after_nodes: 1
271
272# Set the timeout to initiate the recovery process, once the N nodes
273# from previous setting are up (accepts time value):
274#
275# gateway.recover_after_time: 5m
276
277# Set how many nodes are expected in this cluster. Once these N nodes
278# are up (and recover_after_nodes is met), begin recovery process immediately
279# (without waiting for recover_after_time to expire):
280#
281gateway.expected_nodes: 1
282
283
284############################# Recovery Throttling #############################
285
286# These settings allow to control the process of shards allocation between
287# nodes during initial recovery, replica allocation, rebalancing,
288# or when adding and removing nodes.
289
290# Set the number of concurrent recoveries happening on a node:
291#
292# 1. During the initial recovery
293#
294# cluster.routing.allocation.node_initial_primaries_recoveries: 4
295#
296# 2. During adding/removing nodes, rebalancing, etc
297#
298# cluster.routing.allocation.node_concurrent_recoveries: 2
299
300# Set to throttle throughput when recovering (eg. 100mb, by default 20mb):
301#
302# indices.recovery.max_bytes_per_sec: 20mb
303
304# Set to limit the number of open concurrent streams when
305# recovering a shard from a peer:
306#
307# indices.recovery.concurrent_streams: 5
308
309
310################################## Discovery ##################################
311
312# Discovery infrastructure ensures nodes can be found within a cluster
313# and master node is elected. Multicast discovery is the default.
314
315# Set to ensure a node sees N other master eligible nodes to be considered
316# operational within the cluster. Its recommended to set it to a higher value
317# than 1 when running more than 2 nodes in the cluster.
318#
319# discovery.zen.minimum_master_nodes: 1
320
321# Set the time to wait for ping responses from other nodes when discovering.
322# Set this option to a higher value on a slow or congested network
323# to minimize discovery failures:
324#
325# discovery.zen.ping.timeout: 3s
326
327# For more information, see
328# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html>
329
330# Unicast discovery allows to explicitly control which nodes will be used
331# to discover the cluster. It can be used when multicast is not present,
332# or to restrict the cluster communication-wise.
333#
334# 1. Disable multicast discovery (enabled by default):
335#
336# discovery.zen.ping.multicast.enabled: false
337#
338# 2. Configure an initial list of master nodes in the cluster
339# to perform discovery when new nodes (master or data) are started:
340#
341# discovery.zen.ping.unicast.hosts: ["host1", "host2:port"]
342
343# EC2 discovery allows to use AWS EC2 API in order to perform discovery.
344#
345# You have to install the cloud-aws plugin for enabling the EC2 discovery.
346#
347# For more information, see
348# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html>
349#
350# See <http://elasticsearch.org/tutorials/elasticsearch-on-ec2/>
351# for a step-by-step tutorial.
352
353# GCE discovery allows to use Google Compute Engine API in order to perform discovery.
354#
355# You have to install the cloud-gce plugin for enabling the GCE discovery.
356#
357# For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-gce>.
358
359# Azure discovery allows to use Azure API in order to perform discovery.
360#
361# You have to install the cloud-azure plugin for enabling the Azure discovery.
362#
363# For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-azure>.
364
365################################## Slow Log ##################################
366
367# Shard level query and fetch threshold logging.
368
369#index.search.slowlog.threshold.query.warn: 10s
370#index.search.slowlog.threshold.query.info: 5s
371#index.search.slowlog.threshold.query.debug: 2s
372#index.search.slowlog.threshold.query.trace: 500ms
373
374#index.search.slowlog.threshold.fetch.warn: 1s
375#index.search.slowlog.threshold.fetch.info: 800ms
376#index.search.slowlog.threshold.fetch.debug: 500ms
377#index.search.slowlog.threshold.fetch.trace: 200ms
378
379#index.indexing.slowlog.threshold.index.warn: 10s
380#index.indexing.slowlog.threshold.index.info: 5s
381#index.indexing.slowlog.threshold.index.debug: 2s
382#index.indexing.slowlog.threshold.index.trace: 500ms
383
384################################## GC Logging ################################
385
386#monitor.jvm.gc.young.warn: 1000ms
387#monitor.jvm.gc.young.info: 700ms
388#monitor.jvm.gc.young.debug: 400ms
389
390#monitor.jvm.gc.old.warn: 10s
391#monitor.jvm.gc.old.info: 5s
392#monitor.jvm.gc.old.debug: 2s
393