Elasticsearch 集群搭建
搭建
防止JVM报错,修改JVM线程信息数:
sysctl -w vm.max_map_count=262144
永久修改:
echo vm.max_map_count=262144 >> /etc/sysctl.conf
sysctl -p
创建docker网络:
docker network ls
docker network create --driver bridge --subnet=172.18.12.0/16 --gateway=172.18.1.1 mynet
查看网络信息:
docker network inspect mynet
准备三个master节点:
cd /mydata/elasticsearch/
for port in $(seq 1 3); \
do \
mkdir -p /mydata/elasticsearch/master-${port}/config
mkdir -p /mydata/elasticsearch/master-${port}/data
chmod -R 777 /mydata/elasticsearch/master-${port}
cat << EOF >/mydata/elasticsearch/master-${port}/config/elasticsearch.yml
cluster.name: my-es #集群的名称,同一个集群该值必须设置成相同的
node.name: es-master-${port} #该节点的名字
node.master: true #该节点有机会成为 master 节点
node.data: false #该节点可以存储数据
network.host: 0.0.0.0
http.host: 0.0.0.0 #所有 http 均可访
http.port: 920${port}
transport.tcp.port: 930${port}
#discovery.zen.minimum_master_nodes: 2 #设置这个参数来保证集群中的节点可以知道其它N个有master资格的节点
discovery.zen.ping_timeout: 30s
discovery.seed_hosts: ["172.18.12.21:9301", "172.18.12.22:9302", "172.18.12.23:9303"] #设置集群中的 Master 节点的初始列表,可以通过这些节点来自动发现其他新加入集群的节点,es7的新增配置
cluster.initial_master_nodes: ["172.18.12.21"] #新集群初始时的候选主节点,es7的新增配置
EOF
docker run --name elasticsearch-node-${port} \
-p 920${port}:920${port} -p 930${port}:930${port} \
--network=mynet --ip 172.18.12.2${port} \
-e ES_JAVA_OPTS="-Xms300m -Xmx300m" \
-v /mydata/elasticsearch/master-${port}/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml \
-v /mydata/elasticsearch/master-${port}/data:/usr/share/elasticsearch/data \
-v /mydata/elasticsearch/master-${port}/plugins:/usr/share/elasticsearch/plugins \
-d elasticsearch:7.4.2
done
三个容器已启动
查看节点:
docker ps
ll
准备三个node节点:
for port in $(seq 4 6); \
do \
mkdir -p /mydata/elasticsearch/node-${port}/config
mkdir -p /mydata/elasticsearch/node-${port}/data
chmod -R 777 /mydata/elasticsearch/node-${port}
cat << EOF >/mydata/elasticsearch/node-${port}/config/elasticsearch.yml
cluster.name: my-es #集群的名称,同一个集群该值必须设置成相同的
node.name: es-node-${port} #该节点的名字
node.master: false #该节点有机会成为 master 节点
node.data: true #该节点可以存储数据
network.host: 0.0.0.0
#network.publish_host: 192.168.56.10 #互相通信 ip,要设置为本机可被外界访问的 ip,否则无法通信
http.host: 0.0.0.0 #所有 http 均可访
http.port: 920${port}
transport.tcp.port: 930${port}
#discovery.zen.minimum_master_nodes: 2 #设置这个参数来保证集群中的节点可以知道其它N个有 master 资格的节点。
discovery.zen.ping_timeout: 30s
discovery.seed_hosts: ["172.18.12.21:9301", "172.18.12.22:9302", "172.18.12.23:9303"] #设置集群中的 Master 节点的初始列表,可以通过这些节点来自动发现其他新加入集群的节点,es7的新增配置
cluster.initial_master_nodes: ["172.18.12.21"] #新集群初始时的候选主节点,es7的新增配置
EOF
docker run --name elasticsearch-node-${port} \
-p 920${port}:920${port} -p 930${port}:930${port} \
--network=mynet --ip 172.18.12.2${port} \
-e ES_JAVA_OPTS="-Xms300m -Xmx300m" \
-v /mydata/elasticsearch/node-${port}/config/elasticsearch.yml:/usr/share/elasticsearch/config/elasticsearch.yml \
-v /mydata/elasticsearch/node-${port}/data:/usr/share/elasticsearch/data \
-v /mydata/elasticsearch/node-${port}/plugins:/usr/share/elasticsearch/plugins \
-d elasticsearch:7.4.2
done
查看node节点信息
docker ps
若启动过程中三个node节点出现启动不成功问题 :由于上面配置没有生效,修改配置,
echo vm.max_map_count=262144 >> /etc/sysctl.conf
sysctl -p
重新启动容器命令:docker start +容器id或容器名,查看容器运行详细信息
docker ps -a
docker start elasticsearch-node-1 elasticsearch-node-2 elasticsearch-node-3
docker start elasticsearch-node-4 elasticsearch-node-5 elasticsearch-node-6
查看ip:
ip addr
查看某个节点的日志:
docker logs elasticsearch-node-1
docker logs elasticsearch-node-2
docker logs elasticsearch-node-3
docker logs elasticsearch-node-4
docker logs elasticsearch-node-5
docker logs elasticsearch-node-6
所有显示出cluster.name": "my-es"等信息,没有报错就是启动成功。
测试集群工作状况
访问虚拟机ip及es端口,每个节点都可以正常访问
给任意节点发送请求:
http://192.168.56.10:9201/_nodes/process?pretty 查看节点状况
http://192.168.56.10:9201/_cluster/stats?pretty 查看集群状态
http://192.168.56.10:9201/_cluster/health?pretty 查看集群健康状况
http://192.168.56.10:9202/_cat/nodes 查看各个节点信息
$ curl localhost:9200/_cat
/_cat/allocation
/_cat/shards
/_cat/shards/{index}
/_cat/master
/_cat/nodes
/_cat/indices
/_cat/indices/{index}
/_cat/segments
/_cat/segments/{index}
/_cat/count
/_cat/count/{index}
/_cat/recovery
/_cat/recovery/{index}
/_cat/health
/_cat/pending_tasks
/_cat/aliases
/_cat/aliases/{alias}
/_cat/thread_pool
/_cat/plugins
/_cat/fielddata
/_cat/fielddata/{fields}
/_cat/nodeattrs
/_cat/repositories
/_cat/snapshots/{repository}
标记*号的就是当前主节点
http://192.168.56.10:9201/_cat/nodes
查看节点健康状况:
http://192.168.56.10:9201/_cat/health
查看集群状态信息:可以查看每个节点的信息
http://192.168.56.10:9201/_cluster/stats?pretty
查看集群所有节点健康状况:
http://192.168.56.10:9201/_cluster/health?pretty
模拟某个节点宕机
主节点es-master-2宕机:
docker stop elasticsearch-node-2
查看节点状态,发现es-master-1成为主节点
重新启动停掉的主节点es-master-2,发现主节点还是es-master-1
docker start elasticsearch-node-2