Open IDIDIR opened 5 years ago
Both services seem to be run out of memory. Try restarting them and monitor their memory usage. Is there anything else on that box that could be using that much RAM? Is it a new installation or a long running one?
@d-mo new installation. I also tried version 4.0.3, there is the same problem there.
available RAM without docker ~16GB. In docker run only this containers.
the first of the two falling containers begins to reboot the logstash.
Max of RAM usage of Elastic (logged stats every 1s from the moment of launch until the fall of both containers with status 139):
2019-07-21 13:42:03 2.091GiB / 19.57GiB mist_elasticsearch_1 1c66ef8abeba
logstash ~25MiB
I'm unable to replicate the problem. In my case the elasticsearch container uses 2.2GB of RAM.
Could there be some other limit configured on your system that's preventing the elasticsearch container from claiming more than 2GB of RAM?
What happens when you run the same container image manually? eg docker run -it elasticsearch:5.6.10
I selectively checked newer container versions (5.6.16 - 7.2.0).
in one of the latest versions there were notifications that vm.max_map_count is not enough
after which I set
sudo sysctl -w vm.max_map_count = 262144
and in the latest versions this notification has been lost, but earlier versions (prior to 6.3.2, still crash with the error described earlier).
I try my set of programs with Linux distribution from Intel (Clear Linux), if it can somehow affect the result.
mist: v4.1.0 OS: Clear Linux (in VMware) RAM: 20GB
containers:
elastic log:
logstash log: