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