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:
13 #plugin.types: "DeleteByQueryPlugin"
15 ##################### Elasticsearch Configuration Example #####################
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>.
21 # The installation procedure is covered at
22 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>.
24 # Elasticsearch comes with reasonable defaults for most settings,
25 # so you can try it out without bothering with configuration.
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].
32 # Any element in the configuration can be replaced with environment variables
33 # by placing them in ${...} notation. For example:
35 # node.rack: ${RACK_ENV_VAR}
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>
41 ################################### Cluster ###################################
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.
46 # cluster.name: elasticsearch
49 #################################### Node #####################################
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:
54 # node.name: "Franz Kafka"
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.
59 # Allow this node to be eligible as a master node (enabled by default):
63 # Allow this node to store data (enabled by default):
67 # You can exploit these settings to design advanced cluster topologies.
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.
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.
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.)
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.
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:
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
106 #################################### Index ####################################
108 # You can set a number of options (such as shard/replica options, mapping
109 # or analyzer definitions, translog settings, ...) for indices globally,
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.
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.
119 # Set the number of shards (splits) of an index (5 by default):
121 # index.number_of_shards: 5
123 # Set the number of replicas (additional copies) of an index (1 by default):
125 # index.number_of_replicas: 1
127 # Note, that for development on a local machine, with small indices, it usually
128 # makes sense to "disable" the distributed features:
130 index.number_of_shards: 1
131 index.number_of_replicas: 0
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:
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_.
142 # The "number_of_shards" is a one-time setting for an index.
144 # The "number_of_replicas" can be increased or decreased anytime,
145 # by using the Index Update Settings API.
147 # Elasticsearch takes care about load balancing, relocating, gathering the
148 # results from nodes, etc. Experiment with different settings to fine-tune
151 # Use the Index Status API (<http://localhost:9200/A/_status>) to inspect
155 #################################### Paths ####################################
156 path.home: /src/test/resources
157 # Path to directory containing configuration (this file and logging.yml):
159 path.conf: /src/test/resources
161 # Path to directory where to store index data allocated for this node.
163 path.data: target/esdata
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: /target/eswork
177 path.logs: /target/eslogs
179 # Path to where plugins are installed:
181 # path.plugins: /path/to/plugins
184 #################################### Plugin ###################################
186 # If a plugin listed here is not installed for current node, the node will not start.
188 # plugin.mandatory: mapper-attachments,lang-groovy
191 ################################### Memory ####################################
193 # Elasticsearch performs poorly when JVM starts swapping: you should ensure that
196 # Set this property to true to lock the memory:
198 # bootstrap.mlockall: true
200 # Make sure that the ES_MIN_MEM and ES_MAX_MEM environment variables are set
201 # to the same value, and that the machine has enough memory to allocate
202 # for Elasticsearch, leaving enough memory for the operating system itself.
204 # You should also make sure that the Elasticsearch process is allowed to lock
205 # the memory, eg. by using `ulimit -l unlimited`.
208 ############################## Network And HTTP ###############################
210 # Elasticsearch, by default, binds itself to the 0.0.0.0 address, and listens
211 # on port [9200-9300] for HTTP traffic and on port [9300-9400] for node-to-node
212 # communication. (the range means that if the port is busy, it will automatically
213 # try the next port).
215 # Set the bind address specifically (IPv4 or IPv6):
217 # network.bind_host: 192.168.0.1
219 # Set the address other nodes will use to communicate with this node. If not
220 # set, it is automatically derived. It must point to an actual IP address.
222 # network.publish_host: 192.168.0.1
224 # Set both 'bind_host' and 'publish_host':
226 # network.host: 192.168.0.1
228 # Set a custom port for the node to node communication (9300 by default):
230 # transport.tcp.port: 9300
232 # Enable compression for all communication between nodes (disabled by default):
234 # transport.tcp.compress: true
236 # Set a custom port to listen for HTTP traffic:
240 # Set a custom allowed content length:
242 # http.max_content_length: 100mb
244 # Disable HTTP completely:
246 # http.enabled: false
249 ################################### Gateway ###################################
251 # The gateway allows for persisting the cluster state between full cluster
252 # restarts. Every change to the state (such as adding an index) will be stored
253 # in the gateway, and when the cluster starts up for the first time,
254 # it will read its state from the gateway.
256 # There are several types of gateway implementations. For more information, see
257 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html>.
259 # The default gateway type is the "local" gateway (recommended):
261 # gateway.type: local
263 # Settings below control how and when to start the initial recovery process on
264 # a full cluster restart (to reuse as much local data as possible when using shared
267 # Allow recovery process after N nodes in a cluster are up:
269 gateway.recover_after_nodes: 1
271 # Set the timeout to initiate the recovery process, once the N nodes
272 # from previous setting are up (accepts time value):
274 # gateway.recover_after_time: 5m
276 # Set how many nodes are expected in this cluster. Once these N nodes
277 # are up (and recover_after_nodes is met), begin recovery process immediately
278 # (without waiting for recover_after_time to expire):
280 gateway.expected_nodes: 1
283 ############################# Recovery Throttling #############################
285 # These settings allow to control the process of shards allocation between
286 # nodes during initial recovery, replica allocation, rebalancing,
287 # or when adding and removing nodes.
289 # Set the number of concurrent recoveries happening on a node:
291 # 1. During the initial recovery
293 # cluster.routing.allocation.node_initial_primaries_recoveries: 4
295 # 2. During adding/removing nodes, rebalancing, etc
297 # cluster.routing.allocation.node_concurrent_recoveries: 2
299 # Set to throttle throughput when recovering (eg. 100mb, by default 20mb):
301 # indices.recovery.max_bytes_per_sec: 20mb
303 # Set to limit the number of open concurrent streams when
304 # recovering a shard from a peer:
306 # indices.recovery.concurrent_streams: 5
309 ################################## Discovery ##################################
311 # Discovery infrastructure ensures nodes can be found within a cluster
312 # and master node is elected. Multicast discovery is the default.
314 # Set to ensure a node sees N other master eligible nodes to be considered
315 # operational within the cluster. Its recommended to set it to a higher value
316 # than 1 when running more than 2 nodes in the cluster.
318 # discovery.zen.minimum_master_nodes: 1
320 # Set the time to wait for ping responses from other nodes when discovering.
321 # Set this option to a higher value on a slow or congested network
322 # to minimize discovery failures:
324 # discovery.zen.ping.timeout: 3s
326 # For more information, see
327 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-zen.html>
329 # Unicast discovery allows to explicitly control which nodes will be used
330 # to discover the cluster. It can be used when multicast is not present,
331 # or to restrict the cluster communication-wise.
333 # 1. Disable multicast discovery (enabled by default):
335 # discovery.zen.ping.multicast.enabled: false
337 # 2. Configure an initial list of master nodes in the cluster
338 # to perform discovery when new nodes (master or data) are started:
340 # discovery.zen.ping.unicast.hosts: ["host1", "host2:port"]
342 # EC2 discovery allows to use AWS EC2 API in order to perform discovery.
344 # You have to install the cloud-aws plugin for enabling the EC2 discovery.
346 # For more information, see
347 # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/modules-discovery-ec2.html>
349 # See <http://elasticsearch.org/tutorials/elasticsearch-on-ec2/>
350 # for a step-by-step tutorial.
352 # GCE discovery allows to use Google Compute Engine API in order to perform discovery.
354 # You have to install the cloud-gce plugin for enabling the GCE discovery.
356 # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-gce>.
358 # Azure discovery allows to use Azure API in order to perform discovery.
360 # You have to install the cloud-azure plugin for enabling the Azure discovery.
362 # For more information, see <https://github.com/elasticsearch/elasticsearch-cloud-azure>.
364 ################################## Slow Log ##################################
366 # Shard level query and fetch threshold logging.
368 #index.search.slowlog.threshold.query.warn: 10s
369 #index.search.slowlog.threshold.query.info: 5s
370 #index.search.slowlog.threshold.query.debug: 2s
371 #index.search.slowlog.threshold.query.trace: 500ms
373 #index.search.slowlog.threshold.fetch.warn: 1s
374 #index.search.slowlog.threshold.fetch.info: 800ms
375 #index.search.slowlog.threshold.fetch.debug: 500ms
376 #index.search.slowlog.threshold.fetch.trace: 200ms
378 #index.indexing.slowlog.threshold.index.warn: 10s
379 #index.indexing.slowlog.threshold.index.info: 5s
380 #index.indexing.slowlog.threshold.index.debug: 2s
381 #index.indexing.slowlog.threshold.index.trace: 500ms
383 ################################## GC Logging ################################
385 #monitor.jvm.gc.young.warn: 1000ms
386 #monitor.jvm.gc.young.info: 700ms
387 #monitor.jvm.gc.young.debug: 400ms
389 #monitor.jvm.gc.old.warn: 10s
390 #monitor.jvm.gc.old.info: 5s
391 #monitor.jvm.gc.old.debug: 2s