Having a werid issue where elasticsearch is using a lot of memory. I have
the jvm settings to not use more then 1g but its using about 7gb of memory.
Linux is reporting it using about 1g as it should be. But when i kill the
proc all the memory gets flushed.
Where do you see that 7GB is used, node stats api? The jvm setting
ES_HEAP_SIZE only sets the jvm heapspace which is just one part of the
total memory that ES uses.
Having a werid issue where elasticsearch is using a lot of memory. I have
the jvm settings to not use more then 1g but its using about 7gb of memory.
Linux is reporting it using about 1g as it should be. But when i kill the
proc all the memory gets flushed.
Where do you see that 7GB is used, node stats api? The jvm setting
ES_HEAP_SIZE only sets the jvm heapspace which is just one part of the
total memory that ES uses.
Having a werid issue where elasticsearch is using a lot of memory. I have
the jvm settings to not use more then 1g but its using about 7gb of memory.
Linux is reporting it using about 1g as it should be. But when i kill the
proc all the memory gets flushed.
--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
If you did not set ES_DIRECT_SIZE, the memory usage for direct buffers is
unlimited by default. That means the JVM lends memory from the OS until the
OS does not have any more. It's not a bug, it's a feature to exploit the OS
for best performance and resource usage.
If you did not set ES_DIRECT_SIZE, the memory usage for direct buffers is
unlimited by default. That means the JVM lends memory from the OS until the
OS does not have any more. It's not a bug, it's a feature to exploit the OS
for best performance and resource usage.
So i set the value that you pointed out to 2g. and i have Xmx at 1gb but i
am still using about 3.5gb of really memory and 999mb of swap. but htop is
reporting that its only using 17.1% of memory
If you did not set ES_DIRECT_SIZE, the memory usage for direct buffers is
unlimited by default. That means the JVM lends memory from the OS until the
OS does not have any more. It's not a bug, it's a feature to exploit the OS
for best performance and resource usage.
Still wondering about your machine, what OS and if JVM is 32/64 bit.
If you have only 4g RAM total, and OS and file system cache take their
space, then you have much less than 2g heap for ES, maybe just 1g which is
the standard config.
I suggest 32bit JVM and running with standard config.
Still wondering about your machine, what OS and if JVM is 32/64 bit.
If you have only 4g RAM total, and OS and file system cache take their
space, then you have much less than 2g heap for ES, maybe just 1g which is
the standard config.
I suggest 32bit JVM and running with standard config.
Still wondering about your machine, what OS and if JVM is 32/64 bit.
If you have only 4g RAM total, and OS and file system cache take their
space, then you have much less than 2g heap for ES, maybe just 1g which is
the standard config.
I suggest 32bit JVM and running with standard config.
Your settings seem too high for 4g total RAM. You allocate Java Program
Binary (~100m) + Stack (~100m) + Heap (1g) + direct buffers (2g) which
alone is ~3,5g and is far more than recommended 4g / 2 = 2g, so it is not
surprisingly using swap memory.
Please do not set direct buffer to 2g, this makes no sense on 4g total RAM
machine.
Also, you use 64bit Java, which uses more memory than 32bit Java. Note that
32bit Java does not make use of direct buffers. Did you try 32bit Java by
using option -d32 ?
I can increases the ram, the vm is inside of a dedicated server that I own.
I been running this machine for months and never had a memory issue so its
just very werid that it is coming up now.
Your settings seem too high for 4g total RAM. You allocate Java Program
Binary (~100m) + Stack (~100m) + Heap (1g) + direct buffers (2g) which
alone is ~3,5g and is far more than recommended 4g / 2 = 2g, so it is not
surprisingly using swap memory.
Please do not set direct buffer to 2g, this makes no sense on 4g total RAM
machine.
Also, you use 64bit Java, which uses more memory than 32bit Java. Note
that 32bit Java does not make use of direct buffers. Did you try 32bit Java
by using option -d32 ?
I can increases the ram, the vm is inside of a dedicated server that I
own. I been running this machine for months and never had a memory issue so
its just very werid that it is coming up now.
Your settings seem too high for 4g total RAM. You allocate Java Program
Binary (~100m) + Stack (~100m) + Heap (1g) + direct buffers (2g) which
alone is ~3,5g and is far more than recommended 4g / 2 = 2g, so it is not
surprisingly using swap memory.
Please do not set direct buffer to 2g, this makes no sense on 4g total
RAM machine.
Also, you use 64bit Java, which uses more memory than 32bit Java. Note
that 32bit Java does not make use of direct buffers. Did you try 32bit Java
by using option -d32 ?
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.