On Tue, Sep 9, 2014 at 6:55 AM, Thomas <thomas.bo...@gmail.com> wrote:
> By setting this parameter, some additional questions of mine have been > generated: > > By setting indices.memory.index_buffer_size to a specific node and not to > all nodes of the cluster, will this configuration be taken into account > from all nodes? Is it going to be cluster wide or only for index operations > of the specific node? So do I need to set this up to all nodes one by one, > do a restart and then see the effects? > How did you set it for one node? I believe (not certain!) this is supposed to be a global (cluster wide) setting... > Finally, if we index data into an index of 10 shards and I have 5 nodes, > that means that the particular node will index to 2 shards, so > the indices.memory.index_buffer_size will refer to those specific two > shards? > The setting is divided up among all active shards that node is hosting. Once a shard goes "idle" (hasn't seen indexing operation for N minutes) then its RAM buffer is dropped to something tiny, and this returns that RAM to be divided up among the remaining active shards. As of 1.4.0 the stats API will now tell you much RAM buffer was allocated for each shard: https://github.com/elasticsearch/elasticsearch/pull/7440 Mike McCandless http://blog.mikemccandless.com -- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/CAD7smRfYJv5FGxSNbgReUFD%2Bdgz4LOBLkLw0_XmvqnGX5vnNVg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
