Question

我已经设置了Stateful ElasticSearch集群。我们达到了约120请求/秒。新创建的群集比AWS托管的ES群集要慢。

要在Kubernetes上配置ES集群，我们使用了3个i3.xlarge ec2实例。我已经按照https://github.com/pires/kubernetes-elasticsearch-cluster/tree/master/stateful中提到的步骤进行操作。当前，我们不使用Ingest节点，而是使用带两个输出的logstash，即1来管理aws上的ES集群，另一个用于在kubernetes上创建的ES集群。

output {
  amazon_es {
    hosts => ["managed-aws-es"]
    region => "ap-southeast-1"
    index => "logstash-%{type}-%{+YYYY.MM.dd}"
    flush_size => 10
  }

  elasticsearch {
    hosts => ["kubernetes-es:9200"]
    index => "logstash-%{type}-%{+YYYY.MM.dd}"
  }
}

当前配置为3个主节点和3个数据节点。

由于在创建集群时出现错误，因此我将Network_host从“ eth0”更改为“ 0.0.0.0”。

我正在报告此问题，因为我们在托管AWS ES上的延迟不到一分钟，而在kubernetes ES上，群集的延迟却高达15分钟。

更新：我将Network_host更改为eth0：ipv4，我仍然遇到相同的问题

更新：我正在日志中关注味精

[2018-08-17T20:49:06,154][WARN ][o.e.d.s.f.s.h.UnifiedHighlighter] The length [1027571] of [response] field of [OgelSWUBdpiv2jsFhUQ-] doc of [packetbeat-2018.08.17] index has exceeded the allowed maximum of [1000000] set for the next major Elastic version. This maximum can be set by changing the [index.highlight.max_analyzed_offset] index level setting. For large texts, indexing with offsets or term vectors is recommended!

[2018-08-17T20:49:06,325][INFO ][o.e.m.j.JvmGcMonitorService] [es-data-0] [gc][2862] overhead, spent [336ms] collecting in the last [1s]
[2018-08-17T20:49:29,343][INFO ][o.e.m.j.JvmGcMonitorService] [es-data-0] [gc][2885] overhead, spent [325ms] collecting in the last [1s]

ElasticSearch在kubernetes上运行缓慢

0 个答案: