32
32
# cluster.name: elasticsearch
33
33
34
34
35
- # ################################### Node #####################################
36
-
37
- # Node names are generated dynamically on startup, so you're relieved
38
- # from configuring them manually. You can tie this node to a specific name:
39
- #
40
- # node.name: "Franz Kafka"
41
-
42
- # Every node can be configured to allow or deny being eligible as the master,
43
- # and to allow or deny to store the data.
44
- #
45
- # Allow this node to be eligible as a master node (enabled by default):
46
- #
47
- # node.master: true
48
- #
49
- # Allow this node to store data (enabled by default):
50
- #
51
- # node.data: true
52
-
53
- # You can exploit these settings to design advanced cluster topologies.
54
- #
55
- # 1. You want this node to never become a master node, only to hold data.
56
- # This will be the "workhorse" of your cluster.
57
- #
58
- # node.master: false
59
- # node.data: true
60
- #
61
- # 2. You want this node to only serve as a master: to not store any data and
62
- # to have free resources. This will be the "coordinator" of your cluster.
63
- #
64
- # node.master: true
65
- # node.data: false
66
- #
67
- # 3. You want this node to be neither master nor data node, but
68
- # to act as a "search load balancer" (fetching data from nodes,
69
- # aggregating results, etc.)
70
- #
71
- # node.master: false
72
- # node.data: false
73
-
74
- # Use the Cluster Health API [http://localhost:9200/_cluster/health], the
75
- # Node Info API [http://localhost:9200/_nodes] or GUI tools
76
- # such as <http://www.elasticsearch.org/overview/marvel/>,
77
- # <http://github.com/karmi/elasticsearch-paramedic>,
78
- # <http://github.com/lukas-vlcek/bigdesk> and
79
- # <http://mobz.github.com/elasticsearch-head> to inspect the cluster state.
80
-
81
- # A node can have generic attributes associated with it, which can later be used
82
- # for customized shard allocation filtering, or allocation awareness. An attribute
83
- # is a simple key value pair, similar to node.key: value, here is an example:
84
- #
85
- # node.rack: rack314
86
-
87
- # By default, multiple nodes are allowed to start from the same installation location
88
- # to disable it, set the following:
89
- # node.max_local_storage_nodes: 1
90
-
91
-
92
- # ################################### Index ####################################
93
-
94
- # You can set a number of options (such as shard/replica options, mapping
95
- # or analyzer definitions, translog settings, ...) for indices globally,
96
- # in this file.
97
- #
98
- # Note, that it makes more sense to configure index settings specifically for
99
- # a certain index, either when creating it or by using the index templates API.
100
- #
101
- # See <http://elasticsearch.org/guide/en/elasticsearch/reference/current/index-modules.html> and
102
- # <http://elasticsearch.org/guide/en/elasticsearch/reference/current/indices-create-index.html>
103
- # for more information.
104
-
105
- # Set the number of shards (splits) of an index (5 by default):
106
- #
107
- # index.number_of_shards: 5
108
-
109
- # Set the number of replicas (additional copies) of an index (1 by default):
110
- #
111
- # index.number_of_replicas: 1
112
-
113
- # Note, that for development on a local machine, with small indices, it usually
114
- # makes sense to "disable" the distributed features:
115
- #
116
- index.number_of_shards : 1
117
- index.number_of_replicas : 0
118
-
119
35
# These settings directly affect the performance of index and search operations
120
36
# in your cluster. Assuming you have enough machines to hold shards and
121
37
# replicas, the rule of thumb is:
@@ -140,32 +56,8 @@ index.number_of_replicas: 0
140
56
141
57
# ################################### Paths ####################################
142
58
143
- # Path to directory containing configuration (this file and logging.yml):
144
- #
145
- path.conf : /src/test/resources
146
-
147
- # Path to directory where to store index data allocated for this node.
148
- #
149
- path.data : target/esdata
150
- #
151
- # Can optionally include more than one location, causing data to be striped across
152
- # the locations (a la RAID 0) on a file level, favouring locations with most free
153
- # space on creation. For example:
154
- #
155
- # path.data: /path/to/data1,/path/to/data2
156
-
157
- # Path to temporary files:
158
- #
159
- path.work : target/eswork
160
-
161
- # Path to log files:
162
- #
163
- path.logs : target/eslogs
164
-
165
- # Path to where plugins are installed:
166
- #
167
- # path.plugins: /path/to/plugins
168
59
60
+ path.home : target/eshome
169
61
170
62
# ################################### Plugin ###################################
171
63
0 commit comments