Re: maxDocs different between primary and replica shards

Thanks for your reply Christian. This helped a lot and I eventually learned that this is called the bouncing results problem: http://www.elastic.co/guide/en/elasticsearch/guide/current/_search_options.html#_preference I don't quite understand why it isn't lower cost to make each shard

Re: maxDocs different between primary and replica shards

Hi, Merging of segments and the resulting removal of deleted documents is not coordinated across nodes in Elasticsearch, meaning that the amount of deleted documents can differ between primary and replica shards. Optimising an index down to a single segment does resolve this, but can as noted

Re: maxDocs different between primary and replica shards

Same problem... Bueller? Bueller? On Thursday, May 8, 2014 at 1:07:44 PM UTC-7, Csaba Dezsényi wrote: I exactly have the same issue! Does someone have solution for this? Thanks, Csaba 2013. november 28., csütörtök 14:26:51 UTC+1 időpontban Klaus Brunner a következőt írta: We're

Re: maxDocs different between primary and replica shards

I exactly have the same issue! Does someone have solution for this? Thanks, Csaba 2013. november 28., csütörtök 14:26:51 UTC+1 időpontban Klaus Brunner a következőt írta: We're running Elasticsearch (currently 0.90.6) in what I'd call a replicated architecture: our indexes are quite small