Elasticsearch：集群配置及异常解决

节点1

cluster.name: my-esnode.name: 154transport.tcp.port: 9300transport.tcp.compress: truediscovery.zen.ping.unicast.hosts: ["172.16.254.154:9300", "172.27.28.79:9300"] discovery.zen.minimum_master_nodes: 1network.host: 172.16.254.154http.port: 9200http.cors.enabled: true http.cors.allow-origin: "*"

节点2

cluster.name: my-esnode.name: 79transport.tcp.port: 9300transport.tcp.compress: truediscovery.zen.ping.unicast.hosts: ["172.16.254.154:9300", "172.27.28.79:9300"] discovery.zen.minimum_master_nodes: 1network.host: 172.27.28.79http.port: 9200http.cors.enabled: true http.cors.allow-origin: "*"

遇到的问题

rg.elasticsearch.transport.RemoteTransportException: [79][172.27.28.79:9300][internal:cluster/coordination/join]
Caused by: java.lang.IllegalStateException: failure when sending a validation request to nodeat org.elasticsearch.cluster.coordination.Coordinator$2.onFailure(Coordinator.java:514) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.action.ActionListenerResponseHandler.handleException(ActionListenerResponseHandler.java:59) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1139) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1139) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.transport.InboundHandler.lambda$handleException$2(InboundHandler.java:244) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:633) ~[elasticsearch-7.7.0.jar:7.7.0]at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[?:1.8.0_102]at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[?:1.8.0_102]at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]
Caused by: org.elasticsearch.transport.RemoteTransportException: [154][172.16.254.154:9300][internal:cluster/coordination/join/validate]
Caused by: org.elasticsearch.cluster.coordination.CoordinationStateRejectedException: join validation on cluster state with a different cluster uuid G060izKeRnuTDAW9hXbo9g than local cluster uuid 3WHAqO-IRI6wm3d0h8qfZA, rejectingat org.elasticsearch.cluster.coordination.JoinHelper.lambda$new$4(JoinHelper.java:153) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.xpack.security.transport.SecurityServerTransportInterceptor$ProfileSecuredRequestHandler$1.doRun(SecurityServerTransportInterceptor.java:257) ~[?:?]at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.xpack.security.transport.SecurityServerTransportInterceptor$ProfileSecuredRequestHandler.messageReceived(SecurityServerTransportInterceptor.java:315) ~[?:?]at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:63) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.transport.InboundHandler$RequestHandler.doRun(InboundHandler.java:264) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:692) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-7.7.0.jar:7.7.0]at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[?:1.8.0_102]at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[?:1.8.0_102]at java.lang.Thread.run(Thread.java:745) ~[?:1.8.0_102]
[2020-06-04T11:29:14,178][INFO ][o.e.c.c.JoinHelper       ] [154] failed to join {79}{KaY5z8S6Sx26_0C_NAHCBA}{ynNMlEURQp2ULnw45t8pYw}{172.27.28.79}{172.27.28.79:9300}{dilmrt}{ml.machine_memory=4178505728, ml.max_open_jobs=20, xpack.installed=true, transform.node=true} with JoinRequest{sourceNode={154}{OFvixB0zQROD3DRCW92CPA}{VqSnY7qEQ5mwNQUgQvkjEA}{172.16.254.154}{172.16.254.154:9300}{dilmrt}{ml.machine_memory=4294500352, xpack.installed=true, transform.node=true, ml.max_open_jobs=20}, minimumTerm=10, optionalJoin=Optional.empty}
org.elasticsearch.transport.RemoteTransportException: [79][172.27.28.79:9300][internal:cluster/coordination/join]
Caused by: java.lang.IllegalStateException: failure when sending a validation request to nodeat org.elasticsearch.cluster.coordination.Coordinator$2.onFailure(Coordinator.java:514) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.action.ActionListenerResponseHandler.handleException(ActionListenerResponseHandler.java:59) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1139) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.transport.TransportService$ContextRestoreResponseHandler.handleException(TransportService.java:1139) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.transport.InboundHandler.lambda$handleException$2(InboundHandler.java:244) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:633) ~[elasticsearch-7.7.0.jar:7.7.0]at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[?:1.8.0_102]at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[?:1.8.0_102]at java.lang.Thread.run(Thread.java:745) [?:1.8.0_102]
Caused by: org.elasticsearch.transport.RemoteTransportException: [154][172.16.254.154:9300][internal:cluster/coordination/join/validate]
Caused by: org.elasticsearch.cluster.coordination.CoordinationStateRejectedException: join validation on cluster state with a different cluster uuid G060izKeRnuTDAW9hXbo9g than local cluster uuid 3WHAqO-IRI6wm3d0h8qfZA, rejectingat org.elasticsearch.cluster.coordination.JoinHelper.lambda$new$4(JoinHelper.java:153) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.xpack.security.transport.SecurityServerTransportInterceptor$ProfileSecuredRequestHandler$1.doRun(SecurityServerTransportInterceptor.java:257) ~[?:?]at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.xpack.security.transport.SecurityServerTransportInterceptor$ProfileSecuredRequestHandler.messageReceived(SecurityServerTransportInterceptor.java:315) ~[?:?]at org.elasticsearch.transport.RequestHandlerRegistry.processMessageReceived(RequestHandlerRegistry.java:63) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.transport.InboundHandler$RequestHandler.doRun(InboundHandler.java:264) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingAbstractRunnable.doRun(ThreadContext.java:692) ~[elasticsearch-7.7.0.jar:7.7.0]at org.elasticsearch.common.util.concurrent.AbstractRunnable.run(AbstractRunnable.java:37) ~[elasticsearch-7.7.0.jar:7.7.0]at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) ~[?:1.8.0_102]at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) ~[?:1.8.0_102]at java.lang.Thread.run(Thread.java:745) ~[?:1.8.0_102]

因为该节点之前已经启动过，有历史数据没有清理，把该节点的data文件夹删了，再次启动就行。

Elasticsearch：集群配置及异常解决相关推荐

Elasticsearch集群配置以及REST API使用
ES安装与启动在官网下载压缩包,解压后直接运行bin目录下的.bat文件即可.下载地址戳这里. ES配置集群 Elasticsearch配置集群很简单,只要配置一个集群的名称 ,ES就会自动寻找并 ...
Elasticsearch集群配置
Elasticsearch集群配置报错集群状态查看启动配置 cluster.name: es node.name: node-3 path.data: /home/elasticsearch ...
ElasticSearch 集群配置
elasticsearch的config文件夹里面有两个配置文件:elasticsearch.yml和logging.yml,第一个是es的基本配置文件,第二个是日志配置文件,es也是使用log4j ...
ElasticSearch集群配置IK分词
1.环境介绍操作系统:centos 7.9 elasticsearch版本:7.13.3 IK分词版本:elasticsearch-analysis-ik-7.13.3 IK分词下载地址: http ...
Nginx以及通过Nginx实现tomcat集群配置与负载均衡
Nginx简介启动,停止,和重新加载配置文件命令 Nginx功能正向代理和反向代理的区别反向代理负载均衡 1.RR(默认) 2.权重 3.ip_hash 4.fair(第三方) 5.url_h ...
Redis集群配置和常见异常解决
Redis集群配置和常见异常解决参考文章: (1)Redis集群配置和常见异常解决 (2)https://www.cnblogs.com/hzb462606/p/11121281.html 备忘一下 ...
ElasticSearch入门第二篇：集群配置
这是ElasticSearch 2.4 版本系列的第二篇: ElasticSearch入门第一篇:Windows下安装ElasticSearch ElasticSearch入门第二篇:集群配置 E ...
企业级负载均衡集群——通过fence设备解决集群节点之间争抢资源的现象（FENCE搭建、高可用服务配置详解）
1.FENCE工具的原理及作用 FENCE设备是RHCS集群中必不可少的一个组成部分,通过FENCE设备可以避免因出现不可预知的情况而造成的"脑裂"现象 FENCE设备的出现,就是 ...
解决elasticsearch集群Unassigned Shards无法reroute的问题
1.背景&问题描述接上篇文章https://blog.csdn.net/dhaibo1986/article/details/107564968 在上一篇文章中,由于系统宕机,导致大量索引出 ...

Elasticsearch：集群配置及异常解决

节点1

节点2

遇到的问题

Elasticsearch：集群配置及异常解决相关推荐

最新文章

热门文章