No particular downside to increasing numRecordsToKeep except
there is some additional disk space required and a bit of
bookkeeping.
Frankly, though, that's a bandaid at best. There should be more
information in the logs about _why_ they go into recovery.
If you're indexing while nodes are down
Thanks Erick!
We are using SOLR version 7.0.1.
is there any disadvantages if we increase peer sync size to 1000 ?
We have analysed the GC logs but we have not seen long GC pauses so far.
We tried to find the reason for the full sync, but noting more informative,
but we have seen too many logs
No. There's a "peer sync" that will try to update from the leader's
transaction log if (and only if) the replica has fallen behind. By
"fallen behind" I mean it was unable to accept any updates for
some period of time. The default peer sync size is 100 docs,
you can make it larger see
we are using 3 node solr (64GB ram/8cpu/12GB heap)cloud setup with version
7.X. we have 3 indexes/collection on each node. index size were about
250GB. NRT with 5sec soft /10min hard commit. Sometimes in any one node we
are seeing full index replication started running.. is there any
