|
|
@@ -39,6 +39,15 @@ In order to test how many open files the process can open, start it with
|
|
|
`-Des.max-open-files` set to `true`. This will print the number of open
|
|
|
files the process can open on startup.
|
|
|
|
|
|
+Alternatively, you can retrieve the `max_file_descriptors` for each node
|
|
|
+using the <<cluster-nodes-info>> API, with:
|
|
|
+
|
|
|
+[source,js]
|
|
|
+--------------------------------------------------
|
|
|
+curl localhost:9200/_nodes/process?pretty
|
|
|
+--------------------------------------------------
|
|
|
+
|
|
|
+
|
|
|
[float]
|
|
|
[[setup-configuration-memory]]
|
|
|
==== Memory Settings
|
|
|
@@ -73,7 +82,7 @@ The configuration format is http://www.yaml.org/[YAML]. Here is an
|
|
|
example of changing the address all network based modules will use to
|
|
|
bind and publish to:
|
|
|
|
|
|
-[source,js]
|
|
|
+[source,yaml]
|
|
|
--------------------------------------------------
|
|
|
network :
|
|
|
host : 10.0.0.4
|
|
|
@@ -87,7 +96,7 @@ network :
|
|
|
In production use, you will almost certainly want to change paths for
|
|
|
data and log files:
|
|
|
|
|
|
-[source,js]
|
|
|
+[source,yaml]
|
|
|
--------------------------------------------------
|
|
|
path:
|
|
|
logs: /var/log/elasticsearch
|
|
|
@@ -101,7 +110,7 @@ path:
|
|
|
Also, don't forget to give your production cluster a name, which is used
|
|
|
to discover and auto-join other nodes:
|
|
|
|
|
|
-[source,js]
|
|
|
+[source,yaml]
|
|
|
--------------------------------------------------
|
|
|
cluster:
|
|
|
name: <NAME OF YOUR CLUSTER>
|
|
|
@@ -116,7 +125,7 @@ something like the display hostname. By default ElasticSearch will
|
|
|
randomly pick a Marvel character name from a list of around 3000 names
|
|
|
when your node starts up.
|
|
|
|
|
|
-[source,js]
|
|
|
+[source,yaml]
|
|
|
--------------------------------------------------
|
|
|
node:
|
|
|
name: <NAME OF YOUR NODE>
|
|
|
@@ -133,7 +142,7 @@ add:
|
|
|
[[styles]]
|
|
|
==== Configuration styles
|
|
|
|
|
|
-[source,js]
|
|
|
+[source,yaml]
|
|
|
--------------------------------------------------
|
|
|
{
|
|
|
"network" : {
|
|
|
@@ -146,7 +155,7 @@ It also means that its easy to provide the settings externally either
|
|
|
using the `ES_JAVA_OPTS` or as parameters to the `elasticsearch`
|
|
|
command, for example:
|
|
|
|
|
|
-[source,js]
|
|
|
+[source,sh]
|
|
|
--------------------------------------------------
|
|
|
$ elasticsearch -f -Des.network.host=10.0.0.4
|
|
|
--------------------------------------------------
|
|
|
@@ -170,7 +179,7 @@ file which will resolve to an environment setting, for example:
|
|
|
The location of the configuration file can be set externally using a
|
|
|
system property:
|
|
|
|
|
|
-[source,js]
|
|
|
+[source,sh]
|
|
|
--------------------------------------------------
|
|
|
$ elasticsearch -f -Des.config=/path/to/config/file
|
|
|
--------------------------------------------------
|
|
|
@@ -184,7 +193,7 @@ example, the following creates an index with memory based storage
|
|
|
instead of the default file system based one (the format can be either
|
|
|
YAML or JSON):
|
|
|
|
|
|
-[source,js]
|
|
|
+[source,sh]
|
|
|
--------------------------------------------------
|
|
|
$ curl -XPUT http://localhost:9200/kimchy/ -d \
|
|
|
'
|
|
|
@@ -197,7 +206,7 @@ index :
|
|
|
Index level settings can be set on the node level as well, for example,
|
|
|
within the `elasticsearch.yml` file, the following can be set:
|
|
|
|
|
|
-[source,js]
|
|
|
+[source,yaml]
|
|
|
--------------------------------------------------
|
|
|
index :
|
|
|
store:
|
|
|
@@ -210,7 +219,7 @@ started with the mentioned configuration will store the index in memory
|
|
|
settings override what is set in the node configuration. Of course, the
|
|
|
above can also be set as a "collapsed" setting, for example:
|
|
|
|
|
|
-[source,js]
|
|
|
+[source,sh]
|
|
|
--------------------------------------------------
|
|
|
$ elasticsearch -f -Des.index.store.type=memory
|
|
|
--------------------------------------------------
|
Clinton Gormley