linux7安装elasticsearch-7.4.0集群配置

这个博文说的也详细：https://www.jianshu.com/p/15d6241e7844

PS：这里只讲配置文件具体怎么配置请查看我的其他博文

主节点配置信息：

#集群名称

cluster.name: ES-Cluster

#节点名称

node.name: ES-node1

#是否是master节点

node.master: true

#是否允许该节点存储索引数据

node.data: true

#日志目录

path.logs: /var/log/elasticsearch

#绑定地址

network.host: 0.0.0.0

#http端口

http.port: 9200

#集群主机列表

discovery.seed_hosts: [“10.45.154.236”,“10.45.154.70”]

#启动全新的集群时需要此参数，再次重新启动时此参数可免

#cluster.initial_master_nodes: [“10.45.154.236”]

#集群内同时启动的数据任务个数，默认是2个

cluster.routing.allocation.cluster_concurrent_rebalance: 32

#添加或删除节点及负载均衡时并发恢复的线程个数，默认4个

cluster.routing.allocation.node_concurrent_recoveries: 32

#初始化数据恢复时，并发恢复线程的个数，默认4个

cluster.routing.allocation.node_initial_primaries_recoveries: 32

#存储位置

path.data: /data

#是否开启跨域访问

http.cors.enabled: true

#开启跨域访问后的地址限制，*表示无限制

http.cors.allow-origin: “*”

第二个节点配置如下:

#集群名称

cluster.name: ES-Cluster

#节点名称

node.name: ES-node2

#是否是master节点

node.master: false

#是否允许该节点存储索引数据

node.data: true

#日志目录

path.logs: /var/log/elasticsearch

#绑定地址

network.host: 0.0.0.0

#http端口

http.port: 9200

#集群主机列表

discovery.seed_hosts: [“10.45.154.236”,“10.45.154.70”]

#启动全新的集群时需要此参数，再次重新启动时此参数可免

#cluster.initial_master_nodes: [“10.45.154.236”]

#集群内同时启动的数据任务个数，默认是2个

cluster.routing.allocation.cluster_concurrent_rebalance: 32

#添加或删除节点及负载均衡时并发恢复的线程个数，默认4个

cluster.routing.allocation.node_concurrent_recoveries: 32

#初始化数据恢复时，并发恢复线程的个数，默认4个

cluster.routing.allocation.node_initial_primaries_recoveries: 32

#存储位置

path.data: /data

#是否开启跨域访问

http.cors.enabled: true

#开启跨域访问后的地址限制，*表示无限制

http.cors.allow-origin: “*”

————————————————

ElasticSearch7.4集群需要注意的问题（从节点加入不成功）

把之前启动过，且已经有数据的ElasticSearch7.4文件夹直接复制了一份，然后启动时发现，从节点不能加入主节点。报错如下：

org.elasticsearch.transport.RemoteTransportException: [ES-node2][192.168.200.56:9301][internal:cluster/coordination/join]

Caused by: java.lang.IllegalArgumentException: can't add node {ES-node1}{iZEnDFKbQrCR9bmUy6X14Q}{xhV5mtCkSM6XhDXaP9hWjQ}{192.168.200.56}{192.168.200.56:9300}{dil}{ml.machine_memory=7445065728, ml.max_open_jobs=20, xpack.installed=true}, found existing node {ES-node2}{iZEnDFKbQrCR9bmUy6X14Q}{HIw4HDh1RgSd_Ces0LuTbQ}{192.168.200.56}{192.168.200.56:9301}{dilm}{ml.machine_memory=7445065728, xpack.installed=true, ml.max_open_jobs=20} with the same id but is a different node instance

      at org.elasticsearch.cluster.node.DiscoveryNodes$Builder.add(DiscoveryNodes. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.cluster.coordination.JoinTaskExecutor.execute(JoinTaskExecutor. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.cluster.coordination.JoinHelper$1.execute(JoinHelper. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.cluster.service.MasterService.executeTasks(MasterService. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.cluster.service.MasterService.calculateTaskOutputs(MasterService. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.cluster.service.MasterService.runTasks(MasterService. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.cluster.service.MasterService.access$000(MasterService. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.cluster.service.MasterService$Batcher.run(MasterService. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.cluster.service.TaskBatcher.runIfNotProcessed(TaskBatcher. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.cluster.service.TaskBatcher$BatchedTask.run(TaskBatcher. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.runAndClean(PrioritizedEsThreadPoolExecutor. ~[elasticsearch-7.4.0.jar:7.4.0]

      at org.elasticsearch.common.util.concurrent.PrioritizedEsThreadPoolExecutor$TieBreakingPrioritizedRunnable.run(PrioritizedEsThreadPoolExecutor. ~[elasticsearch-7.4.0.jar:7.4.0]

      at ~[?:1.8.0_201]

      at ~[?:1.8.0_201]

      at [?:1.8.0_201]

解决：把data删除从新启动