elasticsearch ElasticSearch:observer:来自群集服务的超时通知,elasticsearch,logstash,elasticsearch,Logstash" /> elasticsearch ElasticSearch:observer:来自群集服务的超时通知,elasticsearch,logstash,elasticsearch,Logstash" />

elasticsearch ElasticSearch:observer:来自群集服务的超时通知

elasticsearch ElasticSearch:observer:来自群集服务的超时通知,elasticsearch,logstash,elasticsearch,Logstash,我有一个带有3个数据主节点的ElasticSearch集群,一个专用客户端节点和一个日志存储,通过ElasticSearch客户端节点向ElasticSearch集群发送事件 客户端无法连接到群集,并且在日志中看到以下错误:- [2015-10-24 00:18:29,657][DEBUG][action.admin.indices.create] [ESClient] observer: timeout notification from cluster service. timeout se

我有一个带有3个数据主节点的ElasticSearch集群,一个专用客户端节点和一个日志存储,通过ElasticSearch客户端节点向ElasticSearch集群发送事件

客户端无法连接到群集,并且在日志中看到以下错误:-

[2015-10-24 00:18:29,657][DEBUG][action.admin.indices.create] [ESClient] observer: timeout notification from cluster service. timeout setting [1m], time since start [1m]
[2015-10-24 00:18:30,743][DEBUG][action.admin.indices.create] [ESClient] no known master node, scheduling a retry
我已经看过了答案,但它对我不起作用。我的主数据弹性搜索配置如下所示:-

cluster.name: elasticsearch
node.name: "ESMasterData1"
node.master: true
node.data: true
index.number_of_shards: 7
index.number_of_replicas: 1
bootstrap.mlockall: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["es-master3:9300", "kibana:9300", "es-master2:9300", "es-master1:9300"]
cloud.aws.access_key: AK
cloud.aws.secret_key: J0
cluster.name: elasticsearch
node.name: "ESClient"
node.master: false
node.data: false
index.number_of_shards: 7
index.number_of_replicas: 1
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["es-master1:9300", "es-master2:9300", "es-master3:9300", "kibana:9300"]
bootstrap.mlockall: true
cloud.aws.access_key: AK
cloud.aws.secret_key: J0
ES客户端配置如下所示:-

cluster.name: elasticsearch
node.name: "ESMasterData1"
node.master: true
node.data: true
index.number_of_shards: 7
index.number_of_replicas: 1
bootstrap.mlockall: true
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["es-master3:9300", "kibana:9300", "es-master2:9300", "es-master1:9300"]
cloud.aws.access_key: AK
cloud.aws.secret_key: J0
cluster.name: elasticsearch
node.name: "ESClient"
node.master: false
node.data: false
index.number_of_shards: 7
index.number_of_replicas: 1
discovery.zen.ping.multicast.enabled: false
discovery.zen.ping.unicast.hosts: ["es-master1:9300", "es-master2:9300", "es-master3:9300", "kibana:9300"]
bootstrap.mlockall: true
cloud.aws.access_key: AK
cloud.aws.secret_key: J0
节点将所有标准配置(如JVM Heap)设置为30GB,而mlockall设置为true

日志存储输出如下所示:

elasticsearch {
      index => "j-%{env}-%{app}-%{iver}-%{[@metadata][app_log_time]}"
      cluster => "elasticsearch"
      host => "kibana"
      port => "9300"
      protocol => "transport"
    }
从ES客户端节点到端口9300上的ES主数据节点,Telnet工作正常。此外,所有三个ES主数据节点都能够相互通信。我还使用iperf验证了客户端和数据主机之间是否启用了TCP和UDP

我在Debian7上使用弹性搜索版本1.7.1


有人能告诉我出了什么问题或者我如何调试吗?

您的三个数据/主节点和客户端节点是否有可能托管在AWS上?没有,它们没有托管在AWS@val上。