##################### ElasticSearch 配置示例 #####################
# This file contains an overview of various configuration settings,
# targeted at operations staff. Application developers should
# consult the guide at <>.
# 这个文件包含了各种配置的概览，旨在配置与运行操作相关的东西。
# 应用程序开发人员应该咨询<>
#
# The installation procedure is covered at
# <>.
# 安装过程在这里有<>.
#
#
# ElasticSearch comes with reasonable defaults for most settings,
# so you can try it out without bothering with configuration.
# ElasticSearch 已经提供了大部分设置，都是合理的默认配置。
# 所以你不必进行烦人的配置就可以尝试一下。
#
# Most of the time, these defaults are just fine for running a production
# cluster. If you're fine-tuning your cluster, or wondering about the
# effect of certain configuration option, please _do ask_ on the
# mailing list or IRC channel [].
# 大多数时候，这些默认的配置就足以运行一个生产集群了。
# 如果你想优化你的集群，或者对一个特定的配置选项的作用好奇，你可以访问邮件列表
# 或者IRC频道[].
#
# Any element in the configuration can be replaced with environment variables
# by placing them in ${...} notation. For example:
# 配置中的任何一个元素都可以被环境变量取代，这些环境变量使用${...}符号占位
# 例如：
# node.rack: ${RACK_ENV_VAR}
# See <>
# for information on supported formats and syntax for the configuration file.
# 查看<>了解更多
# 的可支持的格式和配置文件的语法。
################################### 集群 ###################################
# Cluster name identifies your cluster for auto-discovery. If you're running
# multiple clusters on the same network, make sure you're using unique names.
# 集群名称标识了你的集群，自动探查会用到它。
# 如果你在同一个网络中运行多个集群，那就要确保你的集群名称是独一无二的。
#
# cluster.name: elasticsearch
#################################### 节点 #####################################
# Node names are generated dynamically on startup, so you're relieved
# from configuring them manually. You can tie this node to a specific name:
# 节点名称会在启动的时候自动生成，所以你可以不用手动配置。你也可以给节点指定一个
# 特定的名称
#
# node.name: "Franz Kafka"
# Every node can be configured to allow or deny being eligible as the master,
# and to allow or deny to store the data.
# 每一个节点是否允许被选举成为主节点，是否允许存储数据，都是可以配置的
#
#
# Allow this node to be eligible as a master node (enabled by default):
# 允许这个节点被选举为一个主节点(默认为允许)
#
#
# node.master: true
#
# Allow this node to store data (enabled by default):
# 允许这个节点存储数据(默认为允许)
#
# node.data: true
# You can exploit these settings to design advanced cluster topologies.
# 你可以利用这些设置设计高级的集群拓扑
#
# 1. You want this node to never become a master node, only to hold data.
# This will be the "workhorse" of your cluster.
# 1. 你不想让这个节点成为一个主节点，只想用来存储数据。
# 这个节点会成为你的集群的“负载器”
#
# node.master: false
# node.data: true
#
# 2. You want this node to only serve as a master: to not store any data and
# to have free resources. This will be the "coordinator" of your cluster.
# 2. 你想让这个节点成为一个主节点，并且不用来存储任何数据，并且拥有空闲资源。
# 这个节点会成为你集群中的“协调器”
#
# node.master: true
# node.data: false
#
# 3. You want this node to be neither master nor data node, but
# to act as a "search load balancer" (fetching data from nodes,
# aggregating results, etc.)
# 4. 你既不想让这个节点变成主节点也不想让其变成数据节点，只想让其成为一个“搜索负载均衡器”
# (从节点中获取数据，聚合结果，等等)
#
# node.master: false
# node.data: false
# Use the Cluster Health API [:9200/_cluster/health], the
# Node Info API [:9200/_cluster/nodes] or GUI tools
# such as <> and
# <> to inspect the cluster state.
# 使用集群体检API[:9200/_cluster/health] ,
# 节点信息API[:9200/_cluster/nodes] 或者GUI工具例如：
# <>和<>
# 可以查看集群状态
#