Ah great, many thanks again!
On 20/04/17 17:09, Shalin Shekhar Mangar wrote:
Hi Andrea,
Looks like I have you some bad information. I looked at the code and
ran a test locally. The suggest.build and suggest.reload params are in
fact distributed across to all shards but only to one replica of each
shard. This is still bad enough and you should use buildOnOptimize as
suggested but I just wanted to correct the wrong information I gave
earlier.
On Thu, Apr 20, 2017 at 6:23 PM, Andrea Gazzarini <gxs...@gmail.com> wrote:
Perfect, I don't need NRT at this moment so that fits perfectly
Thanks,
Andrea
On 20/04/17 14:37, Shalin Shekhar Mangar wrote:
Yeah, if it is just once a day then you can afford to do an optimize.
For a more NRT indexing approach, I wouldn't recommend optimize at
all.
On Thu, Apr 20, 2017 at 5:29 PM, Andrea Gazzarini <gxs...@gmail.com>
wrote:
Ok, many thanks
I see / read that it should be better to rely on the background merging
instead of issuing explicit optimizes, but I think in this case one
optimize
in a day it shouldn't be a problem.
Did I get you correctly?
Thanks again,
Andrea
On 20/04/17 13:17, Shalin Shekhar Mangar wrote:
Can the client not send an optimize command explicitly after all
indexing/deleting is complete?
