@@ -7,8 +7,6 @@ Up to this point, we have used a cluster with a single {es} node to get up and
7
7
running with the {stack}. An {es} _node_ is a single server that is part of your
8
8
cluster and stores pieces of your data called _shards_.
9
9
10
- image::security/images/elas_0202.png["A cluster with one node and three primary shards"]
11
-
12
10
You can add more nodes to your cluster and optionally designate specific purposes
13
11
for each node. For example, you can allocate master nodes, data nodes, ingest
14
12
nodes, machine learning nodes, and dedicated coordinating nodes. For details
@@ -28,7 +26,8 @@ When you are deploying a production environment, however, you are generally
28
26
adding nodes on different machines so that your cluster is resilient to outages
29
27
and avoids data loss. In a production scenario, there are additional
30
28
requirements that are not covered in this tutorial. See
31
- {ref}/bootstrap-checks.html#dev-vs-prod-mode[Development vs production mode].
29
+ {ref}/bootstrap-checks.html#dev-vs-prod-mode[Development vs production mode] and
30
+ {ref}/add-elasticsearch-nodes.html[Adding nodes to your cluster].
32
31
33
32
Let's add two nodes to our cluster!
34
33
@@ -162,6 +161,3 @@ Now that you have multiple nodes, your data can be distributed across the
162
161
cluster in multiple primary and replica shards. For more information about the
163
162
concepts of clusters, nodes, and shards, see
164
163
{ref}/getting-started.html[Getting started with {es}].
165
-
166
- image::security/images/elas_0204.png["A cluster with three nodes"]
167
-
0 commit comments