On 3/6/2017 9:06 AM, Chris Ulicny wrote:
> We've recently had some issues with a 5.1.0 core copying the whole index
> when it was set to replicate from a master core.
>
> I've read that if there are documents that have been added to the slave
> core by mistake, it will do a full copy. Though we are
Thanks Erik. I love Mike's video on segment merging.
However I do not believe a large number of merged segments or accidental
optimization is the issue. The data in the core is mostly static and there
is no evidence so far of a large number of merges that took place. Usually
the only updates the i
We need to be pretty nit-picky here.
bq: do a full copy of an index instead of only the necessary files
It's all about "necessary files". "necessary" here means a
all changed segments. Since segments are not changed
after a commit, then replication can safely ignore any segments
files it already
Hi all,
We've recently had some issues with a 5.1.0 core copying the whole index
when it was set to replicate from a master core.
I've read that if there are documents that have been added to the slave
core by mistake, it will do a full copy. Though we are still investigating,
this is probably no
