我已经使用eks kubernetes集群在aws中部署了Elastic-search容器。尽管只有3个索引，但容器的内存使用量一直在增加，而且使用率并不高。我正在使用FluentD将集群容器日志转储到弹性搜索中。除此之外，没有使用elastic-search。我尝试使用 -Xms512m -Xmx512m 应用最小/最大堆大小。它成功地应用了，但内存使用量在24小时内几乎翻了一番。我不确定还需要配置哪些其他选项。我尝试将docker镜像从 elasticsearch:6.5.4 更改为 elasticsearch:6.5.1 。但问题依然存在。我还尝试了 -XX:MaxHeapFreeRatio=50 java选项。

查看来自kibana的屏幕截图。

​

编辑:以下是Elastic-search启动时的日志：

[2019-03-18T13:24:03,119][WARN ][o.e.b.JNANatives         ] [es-79c977d57-v77gw] Unable to lock JVM Memory: error=12, reason=Cannot allocate memory
[2019-03-18T13:24:03,120][WARN ][o.e.b.JNANatives         ] [es-79c977d57-v77gw] This can result in part of the JVM being swapped out.
[2019-03-18T13:24:03,120][WARN ][o.e.b.JNANatives         ] [es-79c977d57-v77gw] Increase RLIMIT_MEMLOCK, soft limit: 16777216, hard limit: 16777216
[2019-03-18T13:24:03,120][WARN ][o.e.b.JNANatives         ] [es-79c977d57-v77gw] These can be adjusted by modifying /etc/security/limits.conf, for example: 
    # allow user 'elasticsearch' mlockall
    elasticsearch soft memlock unlimited
    elasticsearch hard memlock unlimited
[2019-03-18T13:24:03,120][WARN ][o.e.b.JNANatives         ] [es-79c977d57-v77gw] If you are logged in interactively, you will have to re-login for the new limits to take effect.
[2019-03-18T13:24:03,397][INFO ][o.e.e.NodeEnvironment    ] [es-79c977d57-v77gw] using [1] data paths, mounts [[/usr/share/elasticsearch/data (/dev/xvda1)]], net usable_space [38.6gb], net total_space [96.8gb], types [ext4]
[2019-03-18T13:24:03,397][INFO ][o.e.e.NodeEnvironment    ] [es-79c977d57-v77gw] heap size [503.6mb], compressed ordinary object pointers [true]