You must not be worried about the VIRT column in the top display.
In the VIRT column, there is no real memory diaplsyed, but all requests for
virtual address space which is not allocated is shown.
You can VIRT think of all kind of memory requests like direct buffers the
Java JVM wanted to allocate in their lifetime. Only parts of this address
space is active, it's the RSS column.
but iam not able to understand why if i have enought RAM and iam on FC Disk
if i run some query in Kibana i see a very high Load Averege about 8 or 10,
and i perform query on 100 milion documents..
Il giorno lunedì 17 febbraio 2014 18:25:26 UTC+1, Jörg Prante ha scritto:
You must not be worried about the VIRT column in the top display.
In the VIRT column, there is no real memory diaplsyed, but all requests
for virtual address space which is not allocated is shown.
You can VIRT think of all kind of memory requests like direct buffers the
Java JVM wanted to allocate in their lifetime. Only parts of this address
space is active, it's the RSS column.
let me reproduce the usses and then collects all the information needed for
a better examplantion.
as i saw the simple count query for 10 milion events overload my Load
Average even if my quad core still not at 100% , the query ends in about 10
seconds and i cant find any past errors in logs.
iam running ES 1.0.0 with 4 nodes
Il giorno lunedì 17 febbraio 2014 19:57:02 UTC+1, Jörg Prante ha scritto:
Load is a different issue, it is related to the number of processes
running and waiting for the CPU.
What about CPU peaks? Is it just a single query that causes CPU peaks? How
long does the query take to complete?
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.
