setup/important-setting #6
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
自校验出现的一些标点错误
Littlesqx
reviewed
Sep 26, 2018
| other nodes in the cluster. The default name is `elasticsearch`, but you should | ||
| change it to an appropriate name which describes the purpose of the cluster. | ||
| 一个节点只能在与集群所有其他节点共享 `cluster.name` 后才能加入集群。 默认集群名称是 `elasticsearch` ，但你应该 | ||
| 将其更改为描述集群用途的合适名称。 |
There was a problem hiding this comment.
一个节点只能加入一个集群，并且和集群中的所有其他节点共享 cluster.name 。默认集群名称是 elasticsearch ，但你应该将其更改为描述集群用途的合适名称。
| Elasticsearch uses a custom discovery implementation called "Zen Discovery" for | ||
| node-to-node clustering and master election. There are two important discovery | ||
| settings that should be configured before going to production. | ||
| Elasticsearch 使用称为 "Zen Discovery" 的自定义发现实现 node-to-node 集群和主选举。 在投入生产之前应该配置两个重要的发现设置。 | ||
|
|
| connect to other nodes running on the same server. This provides an auto- | ||
| clustering experience without having to do any configuration. | ||
| 开箱即用，没有任何网络配置，Elasticsearch 将绑定到可用的环回地址，并扫描 9300 至 9305 端口以尝试 | ||
| 连接到同一服务器上的其他运行节点。 这提供了一个 auto-clustering 体验，而无需进行任何配置。 |
| When the moment comes to form a cluster with nodes on other servers, you have to | ||
| provide a seed list of other nodes in the cluster that are likely to be live and | ||
| contactable. This can be specified as follows: | ||
| 当需要与其他服务器上的节点组成集群时，你必须提供存活且可达集群中其他节点的种子列表。 可用以下方式指定： |
| having the cluster split into two independent clusters -- a split brain -- which | ||
| will lead to data loss. A more detailed explanation is provided in | ||
| <<split-brain>>. | ||
| 如果没有设置，遭受网络故障的集群有将这个集群分裂成两个独立的集群的风险 -- 脑裂 -- 会导致数据丢失。 |
There was a problem hiding this comment.
如果没有设置，遭受网络故障的集群有将这个集群分裂成两个独立的集群的风险 -- 脑裂（split brain） -- 会导致数据丢失。
| By default, Elasticsearch tells the JVM to use a heap with a minimum and maximum | ||
| size of 1 GB. When moving to production, it is important to configure heap size | ||
| to ensure that Elasticsearch has enough heap available. | ||
| 默认情况下，Elasticsearch 通知 JVM 使用最小和最大值均为 1 GB 的堆。当转到生产时，为了确保 Elasticsearch 有足够的可用堆，因此配置堆大小非常重要。 |
There was a problem hiding this comment.
为了确保 Elasticsearch 有足够的可用堆，配置堆大小非常重要。
|
|
||
| In production use, you will almost certainly want to change the locations of the | ||
| data and log folder: | ||
| 在生产中，你几乎肯定想要改变 data 和 log 文件夹的位置: |
howardhuanghua
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
chapter/chapter2/setup/important-setting 初版翻译完成