|
1 | 1 | [[distributed-cluster]]
|
2 |
| -== Life Inside a Cluster |
| 2 | +== 集群内的原理 |
3 | 3 |
|
4 |
| -.Supplemental Chapter |
| 4 | +.补充章节 |
5 | 5 | ****
|
6 | 6 |
|
7 |
| -As mentioned earlier, this is the first of several supplemental chapters |
8 |
| -about how Elasticsearch operates in a distributed((("clusters"))) environment. In this |
9 |
| -chapter, we explain commonly used terminology like _cluster_, _node_, and |
10 |
| -_shard_, the mechanics of how Elasticsearch scales out, and how it deals with |
11 |
| -hardware failure. |
| 7 | +如前文所述,这是补充章节中第一篇介绍 Elasticsearch 在分布式环境中的运行原理。 |
| 8 | +在这个章节中,我们将会介绍 _cluster_ 、 _node_ 、 _shard_ 等常用术语,Elastisearch 的扩容机制, |
| 9 | +以及如何处理硬件故障的内容。 |
12 | 10 |
|
13 |
| -Although this chapter is not required reading--you can use Elasticsearch for |
14 |
| -a long time without worrying about shards, replication, and failover--it will |
15 |
| -help you to understand the processes at work inside Elasticsearch. Feel free |
16 |
| -to skim through the chapter and to refer to it again later. |
| 11 | +虽然这个章节不是必读的--您完全可以在不关注分片、副本和失效切换等内容的情况下长期使用Elasticseearch-- |
| 12 | +但是这将帮助你了解Elastisearch的内部工作流程。您可以先快速阅览该章节,将来有需要时再次查看。 |
17 | 13 |
|
18 | 14 | ****
|
19 | 15 |
|
20 |
| -Elasticsearch is built to be ((("scalability, Elasticsearch and")))always available, and to scale with your needs. |
21 |
| -Scale can come from buying bigger ((("vertical scaling, Elasticsearch and")))servers (_vertical scale_, or _scaling up_) |
22 |
| -or from buying more ((("horizontal scaling, Elasticsearch and")))servers (_horizontal scale_, or _scaling out_). |
| 16 | +ElasticSearch 的主旨是随时可用和按需扩容。 |
| 17 | +而扩容可以通过购买性能更强大( _垂直扩容_ ,或 _纵向扩容_ )或者数量更多的服务器( _水平扩容_ ,或 _横向扩容_ )来实现。 |
23 | 18 |
|
24 |
| -While Elasticsearch can benefit from more-powerful hardware, vertical scale |
25 |
| -has its limits. Real scalability comes from horizontal scale--the ability to |
26 |
| -add more nodes to the cluster and to spread load and reliability between them. |
| 19 | +虽然 Elasticsearch 可以获益于更强大的硬件设备,但是垂直扩容是有极限的。 |
| 20 | +真正的扩容能力是来自于水平扩容--为集群添加更多的节点,并且将负载压力和稳定性分散到这些节点中。 |
27 | 21 |
|
28 |
| -With most databases, scaling horizontally usually requires a major overhaul of |
29 |
| -your application to take advantage of these extra boxes. In contrast, |
30 |
| -Elasticsearch is _distributed_ by nature: it knows how to manage multiple |
31 |
| -nodes to provide scale and high availability. This also means that your |
32 |
| -application doesn't need to care about it. |
| 22 | +对于大多数的数据库而言,横向扩容意味着彻底改变应用代码,才能利用上新增的资源。 |
| 23 | +与之相反的是,ElastiSearch天生就是 _分布式的_ ,它知道如何通过管理多节点来提高扩容性和可用性。 |
| 24 | +这也意味着你的应用无需关注这个问题。 |
33 | 25 |
|
34 |
| -In this chapter, we show how you can set up your cluster, |
35 |
| -nodes, and shards to scale with your needs and to ensure that your data is |
36 |
| -safe from hardware failure. |
| 26 | +在这个章节中,我们将为您展示如何按您所需配置集群、节点和分片,并且在硬件故障时确保您的数据安全。 |
0 commit comments