master_not_discovered_exception 并且使用ElasticSearch查询索引时也报错,找不到主节点: 代码语言:javascript 复制 {"error":{"root_cause":[{"type":"master_not_discovered_exception","reason":null}],"type":"master_not_discovered_exception","reason":null},"status":503} 并且elasticsearch-head显示: 集群...
自从使用ES以后,每天都能遇到新的报错,今天又是处理异常的一天 Kibana无法启动,报错:找不到主节点: master_not_discovered_exception 并且使用ElasticSearch 1.2K10 广告 云渲染场景解决方案 高性能并发计算、高性能存储等,助力轻资产运营 立即选购 您找到你想要的搜索结果了吗? 是的 没有找到 Kibana配置和启动 "...
"plugin:elasticsearch","error"],"pid":19806,"name":"plugin:elasticsearch","state":"red","message":"Status changed from red to red - Service Unavailable","prevState":"red","prevMsg":"[master_not_discovered_exception] null"}
(master_not_discovered_exception) 删除集群各节点下的data下的数据 rm -rf /usr/elasticsearch/data/* 重启集群 2、修改索引 PUT /my_index/_settings { "number_of_replicas": 1 } {"acknowledged":true} 3、删除索引 DELETE /my_index //删除单个索引 DELETE /index_one,index_two //删除多个索引 ...
nohup sudo -u elasticsearch ./bin/kibana > /www/logs/kibana.log &1 & 4、异常问题 启动失败:no known master node, scheduling a retry或者master_not_discovered_exception 处理办法 node.name 与 cluster.initial_master_nodes 必须是一样的。如果只改一个,另一个取默认值就会出现此问题。
cluster.initial_master_nodes: ["node-1"] network.host: 0.0.0.0 问题五 以上操作都执行完了,但外网还访问不了,需要看一下防火墙是否关闭 # 关闭防火强 systemctl stop firewalld.service # 设置永久关闭 systemctl disable firewalld.service 这里需要注意一点,问题一和二修改完成后需要重启机器,切记、切记、...
the default discovery settings are unsuitable for production use; at least one of [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] must be configured 意思是配置以下三者,最少其一 [discovery.seed_hosts, discovery.seed_providers, cluster.initial_master_nodes] ...
[WARN ][o.e.c.c.ClusterFormationFailureHelper] [node-1] master not discovered or elected yet, an election requires a node with id [rEq_ExihQ927BnwBy3Iz7A], have discovered [] which is not a quorum; discovery will continue using [127.0.0.1:9300, 127.0.0.1:9301, 127.0.0.1:9302, 127...
[WARN ][o.e.c.c.ClusterFormationFailureHelper] [node-1] master not discovered or elected yet, an election requires a node with id [rEq_ExihQ927BnwBy3Iz7A], have discovered [] which is not a quorum; discovery will continue using [127.0.0.1:9300, 127.0.0.1:9301, 127.0.0.1:9302, 127...
MasterNotDiscoveredException[null] at org.elasticsearch.action.support.master.TransportMasterNodeAction$AsyncSingleAction$5.onTimeout(TransportMasterNodeAction.java:226) at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:236) ...