What is my actual index_buffer_size?


(R. Toma) #1

Hi group,

Anyone know how to query the actuel index_buffer_size?
I have searched thru the _cluster/stats output, but cannot find it.

Using 3-node ES 1.0.1 for a logsearch platform (lots of logstash bulking,
less kibana querying) with fresh indices every day, I have
indices.memory.index_buffer_size=50% for a total heap of 32GB.

I have a believe 50% is far too high, but cannot find a metric to prove
this.

Any help is appreciated!

Regards,
Renzo

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/808da292-513c-491a-a3ac-fb220125cb74%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


(Jörg Prante) #2

You can not measure the actual index_buffer_size by API. It is a dynamic
setting, ES adapts its size regularly in the background, depending on
indexing activity. The number is a maximum estimated value. 50% is a good
value for bulk indexing in comparison to the default 10%. It means,
indexing service is allowed to allocate up to 50% of the available heap
memory of a node for buffering data (mostly large docs). Note, it does not
mean that always 50% of all the heap memory is reserved and not available
any more for other components. It is just a high water mark for the
indexing service, just one step in the whole indexing process. There are
more knobs that are also important for bulk indexing performance.

Jörg

On Sun, May 4, 2014 at 9:28 PM, R. Toma renzo.toma@gmail.com wrote:

Hi group,

Anyone know how to query the actuel index_buffer_size?
I have searched thru the _cluster/stats output, but cannot find it.

Using 3-node ES 1.0.1 for a logsearch platform (lots of logstash bulking,
less kibana querying) with fresh indices every day, I have
indices.memory.index_buffer_size=50% for a total heap of 32GB.

I have a believe 50% is far too high, but cannot find a metric to prove
this.

Any help is appreciated!

Regards,
Renzo

--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/808da292-513c-491a-a3ac-fb220125cb74%40googlegroups.comhttps://groups.google.com/d/msgid/elasticsearch/808da292-513c-491a-a3ac-fb220125cb74%40googlegroups.com?utm_medium=email&utm_source=footer
.
For more options, visit https://groups.google.com/d/optout.

--
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAKdsXoHZsohFeM8aup0v8noj983bok1wBS9y4%3DB-Nr7fUqGfrQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


(system) #3