Indices.memory.index_buffer_size. documentation is ambiguous

Continuing the discussion from Index_buffer_size vs max_index_buffer_size:

it says:
"The min and max are taken into account only when index_buffer_size is a percentage. In that case the min and max may override index_buffer_size depending on how much memory is available.

I'll see if we can get the docs updated to reflect this."

since the documentation is not updated yet - I will leave my assumptions/thoughts here. Maybe someone will respond.

So for me it is very hard to understand what does it mean to have two limiting values for the same amount at the same time:

if by default index_buffer_size is 10% of heap size and max_index_bufer_size - is entire heap size.

what does it look like on (for example) a cluster node wtih 32GB heap size:

index_buffer_size is 10% (or 3.2 GB in bulk numbers)
index_max_index_buffer_size is 32 GB ?

In other words with such configuration we say for the indexing : U can use 10% of the heap but not more than all the heap?
And then - what happens in between then?

can someone explain what happens when indexing heap usage exceeds 3.2 GB?

Thank you in advance.

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