ES集群安装错误记录

yangkei

已于 2022-09-13 17:19:20 修改

阅读量6k

点赞数 1

文章标签： elasticsearch 大数据搜索引擎

于 2022-09-05 16:05:02 首次发布

本文链接：https://blog.csdn.net/yangkei/article/details/126707321

版权

本文记录了在安装Elasticsearch集群过程中遇到的常见问题及解决方案，包括JVM堆大小设置不当、network.host配置错误、集群节点未正确启动、密码设置问题以及SSL证书加载失败等。通过对配置文件的调整和检查，成功解决了这些问题。

摘要由CSDN通过智能技术生成

1. JVM设置不合理。
bootstrap check failure [1] of [1]: initial heap size [67108864] not equal to maximum heap size [3221225472]; this can cause resize pauses
原因分析：设置的jvm.options里heap参数不合理，超过操作系统可分配的，需要进行适当的调整。
## -Xms4g
## -Xmx4g
2. network.host配置的域名IP不能对应。
[2022-09-05T01:30:14,364][INFO ][o.e.x.s.c.f.PersistentCache] [es-goya01] persistent cache index loaded
[2022-09-05T01:30:14,365][INFO ][o.e.x.d.l.DeprecationIndexingComponent] [es-goya01] deprecation component started
[2022-09-05T01:30:15,200][ERROR][o.e.b.Elasticsearch      ] [es-goya01] fatal exception while booting Elasticsearchorg.elasticsearch.transport.BindTransportException: Failed to bind to [fe80::44da:d53d:e95a:6be6]:[9300-9399]
   at org.elasticsearch.server@8.4.0/org.elasticsearch.transport.TcpTransport.bindToPort(TcpTransport.java:486)
   at org.elasticsearch.server@8.4.0/org.elasticsearch.transport.TcpTransport.bindServer(TcpTransport.java:447)
   at org.elasticsearch.transport.netty4@8.4.0/org.elasticsearch.transport.netty4.Netty4Transport.doStart(Netty4Transport.java:142)
   at org.elasticsearch.security@8.4.0/org.elasticsearch.xpack.core.security.transport.netty4.SecurityNetty4Transport.doStart(SecurityNetty4Transport.java:96)
   at org.elasticsearch.security@8.4.0/org.elasticsearch.xpack.security.transport.netty4.SecurityNetty4ServerTransport.doStart(SecurityNetty4ServerTransport.java:59)
See logs for more details.
ERROR: Elasticsearch did not exit normally - check the logs at /app/elasticsearch/logs/es840-cluster.log
#这里如果写成域名就需要/etc/hosts里添加ip域名信息，或者直接写成IP地址。否则启动elasticsearch会报“Failed to bind to xxx”错误。

3.ClusterFormationFailureHelper，如果报这个错误，需要将三个节点都启动。
[2022-09-05T02:01:03,396][INFO ][o.e.b.BootstrapChecks ] [es-goya01] bound or publishing to a non-loopback address, enforcing bootstrap checks
[2022-09-05T02:01:03,398][INFO ][o.e.c.c.ClusterBootstrapService] [es-goya01] this node has not joined a bootstrapped cluster yet; [cluster.initial_master_nodes] is set to [es-goya01, es-goya02, es-goya03]
[2022-09-05T02:01:13,407][WARN ][o.e.c.c.ClusterFormationFailureHelper] [es-goya01] master not discovered yet, this node has not previously joined a bootstrapped cluster, and this node must discover master-eligible nodes [es-goya01, es-goya02, es-goya03] to bootstrap a cluster: have discovered [{es-goya01}{wbTopYh5QnGFRWBbJSKulA}{xgqHLLkYS6qR1yGgy1sbRA}{es-goya01}{goya1}{192.168.88.5:9300}{cdfhilmrstw}]; discovery will continue using [] from hosts providers and [{es-goya01}{wbTopYh5QnGFRWBbJSKulA}{xgqHLLkYS6qR1yGgy1sbRA}{es-goya01}{goya1}{192.168.88.5:9300}{cdfhilmrstw}] from last-known cluster state; node term 0, last-accepted version 0 in term 0
[2022-09-05T02:01:23,409][WARN ][o.e.c.c.ClusterFormationFailureHelper] [es-go