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