ElasaticSearch Killed

Elastic Stack Elasticsearch
1

When I try to run the Elasticsearch it says "Killed" and shows the following error.
Error Log
[2021-05-10T11:56:50.233+0000][15547][gc] Using Concurrent Mark Sweep
[2021-05-10T11:56:50.233+0000][15547][gc,heap,coops] Heap address: 0x00000000c0000000, size: 1024 MB, Compressed Oops mode: 32-bit
[2021-05-10T11:56:50.426+0000][15547][safepoint ] Entering safepoint region: EnableBiasedLocking
[2021-05-10T11:56:50.426+0000][15547][safepoint ] Leaving safepoint region
[2021-05-10T11:56:50.426+0000][15547][safepoint ] Total time for which application threads were stopped: 0.0000889 seconds, Stopping threads took: 0.0000465 seconds
[2021-05-10T11:56:50.432+0000][15547][gc,heap,exit ] Heap
[2021-05-10T11:56:50.432+0000][15547][gc,heap,exit ] par new generation total 76672K, used 4089K [0x00000000c0000000, 0x00000000c5330000, 0x00000000c5330000)
[2021-05-10T11:56:50.432+0000][15547][gc,heap,exit ] eden space 68160K, 6% used [0x00000000c0000000, 0x00000000c03fe7f0, 0x00000000c4290000)
[2021-05-10T11:56:50.432+0000][15547][gc,heap,exit ] from space 8512K, 0% used [0x00000000c4290000, 0x00000000c4290000, 0x00000000c4ae0000)
[2021-05-10T11:56:50.432+0000][15547][gc,heap,exit ] to space 8512K, 0% used [0x00000000c4ae0000, 0x00000000c4ae0000, 0x00000000c5330000)
[2021-05-10T11:56:50.432+0000][15547][gc,heap,exit ] concurrent mark-sweep generation total 963392K, used 0K [0x00000000c5330000, 0x0000000100000000, 0x0000000100000000)
[2021-05-10T11:56:50.432+0000][15547][gc,heap,exit ] Metaspace used 3143K, capacity 4480K, committed 4480K, reserved 1056768K
[2021-05-10T11:56:50.432+0000][15547][gc,heap,exit ] class space used 270K, capacity 384K, committed 384K, reserved 1048576K
[2021-05-10T11:56:50.432+0000][15547][safepoint ] Application time: 0.0043303 seconds
[2021-05-10T11:56:50.432+0000][15547][safepoint ] Entering safepoint region: Halt

  • AWS t2.micro (bitnami LAMP)
    ~ java -version output is given below.

openjdk version "11.0.11" 2021-04-20
OpenJDK Runtime Environment (build 11.0.11+9-post-Debian-1deb10u1)
OpenJDK 64-Bit Server VM (build 11.0.11+9-post-Debian-1deb10u1, mixed mode, sharing)

Can someone please put me in the right direction. I am new to ElasticSearch.
Thanks

2

Welcome to our community! :smiley:

That looks like the GC log, what is in your Elasticsearch log?

3

I accidentally deleted the ES log and now all it is creating GC logs. I am not sure how to reproduce the ES log again..

4

You will probably need to restart the Elasticsearch process.

5

Hi ...
I am getting the error now when I try to start the ES. It says that insufficient memory for the Java Runtime Environment. Below is the error statement.
I am running t2.micro (AWS ec2 - 1Gib Memory) instance. I understand that I need to increase instance size for memory but what's the best and economical solution? I am setting up ES for starting to medium level Magento store.

Error Statement

warning: usage of JAVA_HOME is deprecated, use ES_JAVA_HOME
	warning: usage of JAVA_HOME is deprecated, use ES_JAVA_HOME
	OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecated in version 9.0 and will likely be removed in a future release.
	OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x00007f1b7d00c000, 262144, 0) failed; error='Not enough space' (errno=12)
	#
	# There is insufficient memory for the Java Runtime Environment to continue.
	# Native memory allocation (mmap) failed to map 262144 bytes for committing reserved memory.
	# An error report file with more information is saved as:
	# logs/hs_err_pid1166.log
6

How much HEAP did you give to the jvm?

Note that you could also run the smallest instance in cloud.elastic.co. The price starts from around $14 a month.
The advantage is that everything is deployed including a Kibana instance and secured.

7

Also fix this:

8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.