Had previously set up ES6 feel quite easy, I did not expect time to re-learn ES7 today, own three linux to toss middle of the night more than two points. . Profile 7.1 and 6 and a little different. . The stickers of their own tests available
In addition to linux some settings number of threads (the Internet easier to find), there can not be (their new one, remember to assign permissions) with the root user, it must JDK11 (this can be backward compatible, but will report a reminder), mainly spent most of the time this configuration file in tune, I host three machines are slave1 slave2 slave3
[root@slave1 config]# cat elasticsearch.yml
# ======================== Elasticsearch Configuration =========================
#
# NOTE: Elasticsearch comes with reasonable defaults for most settings.
# Before you set out to tweak and tune the configuration, make sure you
# understand what are you trying to accomplish and the consequences.
#
# The primary way of configuring a node is via this file. This template lists
# the most important settings you may want to configure for a production cluster.
#
# Please consult the documentation for further information on configuration options:
# https://www.elastic.co/guide/en/elasticsearch/reference/index.html
#
# ---------------------------------- Cluster -----------------------------------
#
# Use a descriptive name for your cluster:
#集群的唯一名字
cluster.name: dianping-app
#
# ------------------------------------ Node ------------------------------------
#
# Use a descriptive name for the node:
#
node.name: node-1
#
# Add custom attributes to the node:
#
#node.attr.rack: r1
#
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
#path.data: /path/to/data
#
# Path to log files:
#
#path.logs: /path/to/logs
#
# ----------------------------------- Memory -----------------------------------
#
# Lock the memory on startup:
#
#bootstrap.memory_lock: true
#
# Make sure that the heap size is set to about half the memory available
# on the system and that the owner of the process is allowed to use this
# limit.
#
# Elasticsearch performs poorly when the system is swapping the memory.
#
# ---------------------------------- Network -----------------------------------
#
# Set the bind address to a specific IP (IPv4 or IPv6):
#集群节点启动在哪个IP上面
network.host: slave1
#
# Set a custom port for HTTP:
#集群RPC通信
http.port: 9200
Communication between cluster #
transport.tcp.port: 9300
http.cors.enabled: to true
# front end over whether to allow access
http.cors.allow-Origin: "*"
#
. # the For More Information, Documentation CONSULT at The Network Module
#
# ------------ --------------------- Discovery ---------------------------- ------
#
# Pass AN Initial List of hosts to the perform the when the this the Node Discovery IS Started:
# List of hosts at The default IS [ "127.0.0.1", "[:: 1]"]
#
discovery.seed_hosts: [ "slave1: 9300", "slave2: 9300", "slave3: 9300"]
#
# Bootstrap at The Cluster of a using the SET AN Initial master-eligible nodes:
# master node are eligible to run for a lot of people here with the port, or by the hostname of the machine, I have tested are not
cluster.initial_master_nodes: [ "node-1" , "node-2", "node-3"]
#
The For More Information #, CONSULT at The Discovery and Documentation Module Cluster formation.
#
# ---------------------------------- ----------------------------------- Gateway
#
# Initial Block A Full Recovery After the restart Cluster Nodes are an until N Started:
#
# gateway.recover_after_nodes: 3
#
. # the For More Information, Documentation CONSULT at The Gateway Module
#
# --------------------------- Various ----------------------------------- -------
#
# the when the Deleting the Require Explicit names indices:
#
# action.destructive_requires_name: to true
#ElasticSearch cluster startup errors, wrong reason is: because Centos6 does not support SecComp, while ES default bootstrap.system_call_filter be detected as to true
bootstrap.memory_lock: false
bootstrap.system_call_filter: false
network.publish_host: slave1