You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
environments, otherwise you might end up with nodes joining the wrong cluster.
619
619
For instance you could use <codeclass="literal">logging-dev</code>, <codeclass="literal">logging-stage</code>, and <codeclass="literal">logging-prod</code>
620
620
for the development, staging, and production clusters.</p><p>Note that it is valid and perfectly fine to have a cluster with only a single node in it. Furthermore, you may also have multiple independent clusters each with its own unique cluster name.</p><h3><aid="_node"></a>Node<ahref="https://github.com/elastic/elasticsearch/edit/5.6/docs/reference/getting-started.asciidoc" class="edit_me" title="Edit this page on GitHub" rel="nofollow">edit</a></h3><p>A node is a single server that is part of your cluster, stores your data, and participates in the cluster’s indexing and search
621
-
capabilities. Just like a cluster, a node is identified by a name which by default is a random Universally Unique IDentifier (UUID) that is assigned to the node at startup. You can define any node name you want if you do not want the default. This name is important for administration purposes where you want to identify which servers in your network correspond to which nodes in your Elasticsearch cluster.</p><p>A node can be configured to join a specific cluster by the cluster name. By default, each node is set up to join a cluster named <codeclass="literal">elasticsearch</code> which means that if you start up a number of nodes on your network and—assuming they can discover each other—they will all automatically form and join a single cluster named <codeclass="literal">elasticsearch</code>.</p><p>In a single cluster, you can have as many nodes as you want. Furthermore, if there are no other Elasticsearch nodes currently running on your network, starting a single node will by default form a new single-node cluster named <codeclass="literal">elasticsearch</code>.</p><h3><aid="_index"></a>Index<ahref="https://github.com/elastic/elasticsearch/edit/5.6/docs/reference/getting-started.asciidoc" class="edit_me" title="Edit this page on GitHub" rel="nofollow">edit</a></h3><p>An index is a collection of documents that have somewhat similar characteristics. For example, you can have an index for customer data, another index for a product catalog, and yet another index for order data. An index is identified by a name (that must be all lowercase) and this name is used to refer to the index when performing indexing, search, update, and delete operations against the documents in it.</p><p>In a single cluster, you can define as many indexes as you want.</p><h3><aid="_type"></a>Type<ahref="https://github.com/elastic/elasticsearch/edit/5.6/docs/reference/getting-started.asciidoc" class="edit_me" title="Edit this page on GitHub" rel="nofollow">edit</a></h3><p>Within an index, you can define one or more types. A type is a logical category/partition of your index whose semantics is completely up to you. In general, a type is defined for documents that have a set of common fields. For example, let’s assume you run a blogging platform and store all your data in a single index. In this index, you may define a type for user data, another type for blog data, and yet another type for comments data.</p><h3><aid="_document"></a>Document<ahref="https://github.com/elastic/elasticsearch/edit/5.6/docs/reference/getting-started.asciidoc" class="edit_me" title="Edit this page on GitHub" rel="nofollow">edit</a></h3><p>A document is a basic unit of information that can be indexed. For example, you can have a document for a single customer, another document for a single product, and yet another for a single order. This document is expressed in <aclass="ulink" href="http://json.org/" target="_top">JSON</a> (JavaScript Object Notation) which is an ubiquitous internet data interchange format.</p><p>Within an index/type, you can store as many documents as you want. Note that although a document physically resides in an index, a document actually must be indexed/assigned to a type inside an index.</p><h3><aid="getting-started-shards-and-replicas"></a>Shards & Replicas<ahref="https://github.com/elastic/elasticsearch/edit/5.6/docs/reference/getting-started.asciidoc" class="edit_me" title="Edit this page on GitHub" rel="nofollow">edit</a></h3><p>An index can potentially store a large amount of data that can exceed the hardware limits of a single node. For example, a single index of a billion documents taking up 1TB of disk space may not fit on the disk of a single node or may be too slow to serve search requests from a single node alone.</p><p>To solve this problem, Elasticsearch provides the ability to subdivide your index into multiple pieces called shards. When you create an index, you can simply define the number of shards that you want. Each shard is in itself a fully-functional and independent "index" that can be hosted on any node in the cluster.</p><p>Sharding is important for two primary reasons:</p><divclass="itemizedlist"><ulclass="itemizedlist" type="disc"><liclass="listitem">
621
+
capabilities. Just like a cluster, a node is identified by a name which by default is a random Universally Unique IDentifier (UUID) that is assigned to the node at startup. You can define any node name you want if you do not want the default. This name is important for administration purposes where you want to identify which servers in your network correspond to which nodes in your Elasticsearch cluster.</p><p>A node can be configured to join a specific cluster by the cluster name. By default, each node is set up to join a cluster named <codeclass="literal">elasticsearch</code> which means that if you start up a number of nodes on your network and—assuming they can discover each other—they will all automatically form and join a single cluster named <codeclass="literal">elasticsearch</code>.</p><p>In a single cluster, you can have as many nodes as you want. Furthermore, if there are no other Elasticsearch nodes currently running on your network, starting a single node will by default form a new single-node cluster named <codeclass="literal">elasticsearch</code>.</p><h3><aid="_index"></a>Index<ahref="https://github.com/elastic/elasticsearch/edit/5.6/docs/reference/getting-started.asciidoc" class="edit_me" title="Edit this page on GitHub" rel="nofollow">edit</a></h3><p>An index is a collection of documents that have somewhat similar characteristics. For example, you can have an index for customer data, another index for a product catalog, and yet another index for order data. An index is identified by a name (that must be all lowercase) and this name is used to refer to the index when performing indexing, search, update, and delete operations against the documents in it.</p><p>In a single cluster, you can define as many indexes as you want.</p><h3><aid="_type"></a>Type<ahref="https://github.com/elastic/elasticsearch/edit/5.6/docs/reference/getting-started.asciidoc" class="edit_me" title="Edit this page on GitHub" rel="nofollow">edit</a></h3><p>Within an index, you can define one or more types. A type is a logical category/partition of your index whose semantics is completely up to you. In general, a type is defined for documents that have a set of common fields. For example, let’s assume you run a blogging platform and store all your data in a single index. In this index, you may define a type for user data, another type for blog data, and yet another type for comments data.</p><h3><aid="_document"></a>Document<ahref="https://github.com/elastic/elasticsearch/edit/5.6/docs/reference/getting-started.asciidoc" class="edit_me" title="Edit this page on GitHub" rel="nofollow">edit</a></h3><p>A document is a basic unit of information that can be indexed. For example, you can have a document for a single customer, another document for a single product, and yet another for a single order. This document is expressed in <aclass="ulink" href="http://json.org/" target="_top">JSON</a> (JavaScript Object Notation) which is a ubiquitous internet data interchange format.</p><p>Within an index/type, you can store as many documents as you want. Note that although a document physically resides in an index, a document actually must be indexed/assigned to a type inside an index.</p><h3><aid="getting-started-shards-and-replicas"></a>Shards & Replicas<ahref="https://github.com/elastic/elasticsearch/edit/5.6/docs/reference/getting-started.asciidoc" class="edit_me" title="Edit this page on GitHub" rel="nofollow">edit</a></h3><p>An index can potentially store a large amount of data that can exceed the hardware limits of a single node. For example, a single index of a billion documents taking up 1TB of disk space may not fit on the disk of a single node or may be too slow to serve search requests from a single node alone.</p><p>To solve this problem, Elasticsearch provides the ability to subdivide your index into multiple pieces called shards. When you create an index, you can simply define the number of shards that you want. Each shard is in itself a fully-functional and independent "index" that can be hosted on any node in the cluster.</p><p>Sharding is important for two primary reasons:</p><divclass="itemizedlist"><ulclass="itemizedlist" type="disc"><liclass="listitem">
622
622
It allows you to horizontally split/scale your content volume
623
623
</li><liclass="listitem">
624
624
It allows you to distribute and parallelize operations across shards (potentially on multiple nodes) thus increasing performance/throughput
0 commit comments