I upgraded to 1.2.1 and set memory options to 2GB. Two weeks have passed
now and every day I have been checking heap memory level with Bigdesk.
At first I was not sure, but now it is clearly increasing little by little.
One day after I restarted ES it grew to approximately 1.3 GB of used Heap
Memory, and now we are at 1.6GB, which make me guess it is leaking around
150 Mo Heap Memory a week.
I am the only one experiencing such problem? And do you know what could
cause it?
I upgraded to 1.2.1 and set memory options to 2GB. Two weeks have passed
now and every day I have been checking heap memory level with Bigdesk.
At first I was not sure, but now it is clearly increasing little by
little. One day after I restarted ES it grew to approximately 1.3 GB of
used Heap Memory, and now we are at 1.6GB, which make me guess it is
leaking around 150 Mo Heap Memory a week.
I am the only one experiencing such problem? And do you know what could
cause it?
I upgraded to 1.2.1 and set memory options to 2GB. Two weeks have passed
now and every day I have been checking heap memory level with Bigdesk.
At first I was not sure, but now it is clearly increasing little by
little. One day after I restarted ES it grew to approximately 1.3 GB of
used Heap Memory, and now we are at 1.6GB, which make me guess it is
leaking around 150 Mo Heap Memory a week.
I am the only one experiencing such problem? And do you know what could
cause it?
Best,
Aldian
--
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.
I upgraded to 1.2.1 and set memory options to 2GB. Two weeks have passed
now and every day I have been checking heap memory level with Bigdesk.
At first I was not sure, but now it is clearly increasing little by
little. One day after I restarted ES it grew to approximately 1.3 GB of
used Heap Memory, and now we are at 1.6GB, which make me guess it is
leaking around 150 Mo Heap Memory a week.
I am the only one experiencing such problem? And do you know what could
cause it?
Best,
Aldian
--
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.
It's entirely normal for ES (or any Java program) to use 75-80% of the heap
during normal operation. The Garbage Collector will take care of things,
and is typically a bit "lazy" about cleaning up.
mike
On Tuesday, June 24, 2014 7:21:49 PM UTC-4, Mark Walkom wrote:
Yes, but there is still overhead that the cluster needs to store in
memory, the metadata about the data.
On 24 June 2014 20:01, Aldian <aldi...@gmail.com <javascript:>> wrote:
Hi
I upgraded to 1.2.1 and set memory options to 2GB. Two weeks have
passed now and every day I have been checking heap memory level with
Bigdesk.
At first I was not sure, but now it is clearly increasing little by
little. One day after I restarted ES it grew to approximately 1.3 GB of
used Heap Memory, and now we are at 1.6GB, which make me guess it is
leaking around 150 Mo Heap Memory a week.
I am the only one experiencing such problem? And do you know what could
cause it?
Best,
Aldian
--
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 elasticsearc...@googlegroups.com <javascript:>.
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.