2 elasticSearch.local: true
3 elasticSearch.transportclient: false
4 cluster.name: elasticsearch
6 discovery.zen.ping.multicast.enabled: false
7 discovery.zen.ping.unicast.enabled: true
8 discovery.zen.ping.unicast.hosts: elasticsearch_host
9 transport.client.initial_nodes:
10 - elasticsearch_host:9300
12 http.cors.enabled: true
14 #plugin.types: "DeleteByQueryPlugin"
16 ##################### Elasticsearch Configuration Example #####################
18 # This file contains an overview of various configuration settings,
19 # targeted at operations staff. Application developers should
20 # consult the guide at <http://elasticsearch.org/guide>.
22 # The installation procedure is covered at
23 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>.
25 # Elasticsearch comes with reasonable defaults for most settings,
26 # so you can try it out without bothering with configuration.
28 # Most of the time, these defaults are just fine for running a production
29 # cluster. If you're fine-tuning your cluster, or wondering about the
30 # effect of certain configuration option, please _do ask_ on the
31 # mailing list or IRC channel [http://elasticsearch.org/community].
33 # Any element in the configuration can be replaced with environment variables
34 # by placing them in ${...} notation. For example:
36 # node.rack: ${RACK_ENV_VAR}
38 # For information on supported formats and syntax for the config file, see
39 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup-configuration.html>
42 ################################### Cluster ###################################
44 # Cluster name identifies your cluster for auto-discovery. If you're running
45 # multiple clusters on the same network, make sure you're using unique names.
47 # cluster.name: elasticsearch
50 #################################### Node #####################################
52 # Node names are generated dynamically on startup, so you're relieved
53 # from configuring them manually. You can tie this node to a specific name:
55 # node.name: "Franz Kafka"
57 # Every node can be configured to allow or deny being eligible as the master,
58 # and to allow or deny to store the data.
60 # Allow this node to be eligible as a master node (enabled by default):
64 # Allow this node to store data (enabled by default):
68 # You can exploit these settings to design advanced cluster topologies.
70 # 1. You want this node to never become a master node, only to hold data.
71 # This will be the "workhorse" of your cluster.
76 # 2. You want this node to only serve as a master: to not store any data and
77 # to have free resources. This will be the "coordinator" of your cluster.
82 # 3. You want this node to be neither master nor data node, but
83 # to act as a "search load balancer" (fetching data from nodes,
84 # aggregating results, etc.)
89 # Use the Cluster Health API [http://localhost:9200/_cluster/health], the
90 # Node Info API [http://localhost:9200/_nodes] or GUI tools
91 # such as <http://www.elasticsearch.org/overview/marvel/>,
92 # <http://github.com/karmi/elasticsearch-paramedic>,
93 # <http://github.com/lukas-vlcek/bigdesk> and
94 # <http://mobz.github.com/elasticsearch-head> to inspect the cluster state.
96 # A node can have generic attributes associated with it, which can later be used
97 # for customized shard allocation filtering, or allocation awareness. An attribute
98 # is a simple key value pair, similar to node.key: value, here is an example:
102 # By default, multiple nodes are allowed to start from the same installation location
103 # to disable it, set the following:
104 # node.max_local_storage_nodes: 1
107 #################################### Index ####################################
109 # You can set a number of options (such as shard/replica options, mapping
110 # or analyzer definitions, translog settings, ...) for indices globally,
113 # Note, that it makes more sense to configure index settings specifically for
114 # a certain index, either when creating it or by using the index templates API.
116 # See <http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html> and
117 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html>
118 # for more information.
120 # Set the number of shards (splits) of an index (5 by default):
122 # index.number_of_shards: 5
124 # Set the number of replicas (additional copies) of an index (1 by default):
126 # index.number_of_replicas: 1
128 # Note, that for development on a local machine, with small indices, it usually
129 # makes sense to "disable" the distributed features:
131 index.number_of_shards: 1
132 index.number_of_replicas: 0
134 # These settings directly affect the performance of index and search operations
135 # in your cluster. Assuming you have enough machines to hold shards and
136 # replicas, the rule of thumb is:
138 # 1. Having more *shards* enhances the _indexing_ performance and allows to
139 # _distribute_ a big index across machines.
140 # 2. Having more *replicas* enhances the _search_ performance and improves the
141 # cluster _availability_.
143 # The "number_of_shards" is a one-time setting for an index.
145 # The "number_of_replicas" can be increased or decreased anytime,
146 # by using the Index Update Settings API.
148 # Elasticsearch takes care about load balancing, relocating, gathering the
149 # results from nodes, etc. Experiment with different settings to fine-tune
152 # Use the Index Status API (<http://localhost:9200/A/_status>) to inspect
156 #################################### Paths ####################################
157 path.home: /src/test/resources
158 # Path to directory containing configuration (this file and logging.yml):
160 path.conf: /src/test/resources
162 # Path to directory where to store index data allocated for this node.
164 path.data: target/esdata
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:
170 # path.data: /path/to/data1,/path/to/data2
172 # Path to temporary files:
174 path.work: /target/eswork
178 path.logs: /target/eslogs
180 # Path to where plugins are installed:
182 # path.plugins: /path/to/plugins
185 #################################### Plugin ###################################
187 # If a plugin listed here is not installed for current node, the node will not start.
189 # plugin.mandatory: mapper-attachments,lang-groovy
192 ################################### Memory ####################################
194 # Elasticsearch performs poorly when JVM starts swapping: you should ensure that
197 # Set this property to true to lock the memory:
199 # bootstrap.mlockall: true
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.
205 # You should also make sure that the Elasticsearch process is allowed to lock
206 # the memory, eg. by using `ulimit -l unlimited`.
209 ############################## Network And HTTP ###############################
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).
216 # Set the bind address specifically (IPv4 or IPv6):
218 # network.bind_host: 192.168.0.1
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.
223 # network.publish_host: 192.168.0.1
225 # Set both 'bind_host' and 'publish_host':
227 # network.host: 192.168.0.1
229 # Set a custom port for the node to node communication (9300 by default):
231 # transport.tcp.port: 9300
233 # Enable compression for all communication between nodes (disabled by default):
235 # transport.tcp.compress: true
237 # Set a custom port to listen for HTTP traffic:
241 # Set a custom allowed content length:
243 # http.max_content_length: 100mb
245 # Disable HTTP completely:
247 # http.enabled: false
250 ################################### Gateway ###################################
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.
257 # There are several types of gateway implementations. For more information, see
258 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html>.
260 # The default gateway type is the "local" gateway (recommended):
262 # gateway.type: local
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
268 # Allow recovery process after N nodes in a cluster are up:
270 gateway.recover_after_nodes: 1
272 # Set the timeout to initiate the recovery process, once the N nodes
273 # from previous setting are up (accepts time value):
275 # gateway.recover_after_time: 5m
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):
281 gateway.expected_nodes: 1
284 ############################# Recovery Throttling #############################
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.
290 # Set the number of concurrent recoveries happening on a node:
292 # 1. During the initial recovery
294 # cluster.routing.allocation.node_initial_primaries_recoveries: 4
296 # 2. During adding/removing nodes, rebalancing, etc
298 # cluster.routing.allocation.node_concurrent_recoveries: 2
300 # Set to throttle throughput when recovering (eg. 100mb, by default 20mb):
302 # indices.recovery.max_bytes_per_sec: 20mb
304 # Set to limit the number of open concurrent streams when
305 # recovering a shard from a peer:
307 # indices.recovery.concurrent_streams: 5
310 ################################## Discovery ##################################
312 # Discovery infrastructure ensures nodes can be found within a cluster
313 # and master node is elected. Multicast discovery is the default.
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.
319 # discovery.zen.minimum_master_nodes: 1
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:
325 # discovery.zen.ping.timeout: 3s
327 # For more information, see
328 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html>
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.
334 # 1. Disable multicast discovery (enabled by default):
336 # discovery.zen.ping.multicast.enabled: false
338 # 2. Configure an initial list of master nodes in the cluster
339 # to perform discovery when new nodes (master or data) are started:
341 # discovery.zen.ping.unicast.hosts: ["host1", "host2:port"]
343 # EC2 discovery allows to use AWS EC2 API in order to perform discovery.
345 # You have to install the cloud-aws plugin for enabling the EC2 discovery.
347 # For more information, see
348 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html>
350 # See <http://elasticsearch.org/tutorials/elasticsearch-on-ec2/>
351 # for a step-by-step tutorial.
353 # GCE discovery allows to use Google Compute Engine API in order to perform discovery.
355 # You have to install the cloud-gce plugin for enabling the GCE discovery.
357 # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-gce>.
359 # Azure discovery allows to use Azure API in order to perform discovery.
361 # You have to install the cloud-azure plugin for enabling the Azure discovery.
363 # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-azure>.
365 ################################## Slow Log ##################################
367 # Shard level query and fetch threshold logging.
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
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
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
384 ################################## GC Logging ################################
386 #monitor.jvm.gc.young.warn: 1000ms
387 #monitor.jvm.gc.young.info: 700ms
388 #monitor.jvm.gc.young.debug: 400ms
390 #monitor.jvm.gc.old.warn: 10s
391 #monitor.jvm.gc.old.info: 5s
392 #monitor.jvm.gc.old.debug: 2s