We made some cache config changes, That is when we noticed incomplete
replicas. We also bootstrap the configuration from script every time server
restarts.
Would cache config changes cause any issue with SolrCloud replication?
mostly when different nodes have different config(cache setting in this
Not at this point, the limit is, I think, 100 documents.
I actually spoke imprecisely. Over that limit, an old-style
replication happens which _may_ cause a full index copy,
but usually will only move over the most recent segments
that have changed. If you're optimizing, this will
be the whole inde
Hi Erick,
The issue was with zookeeper when we tried to force full replication by
cleaning the datadir in zookeeper, caused the index removal.
Our index always replicated full even on short outage or restart. I think
"too far out of date" could be the reason. We felt zookeeper was to blame
here.
That is very odd. Have there been any hard commits performed at all? Even
if not, there should still be an index directory.
Solr will do a full replication if the replica is too far out of date, but
that shouldn't
create (I don't think) a new index directory unless it's a misleading
message.
Is th
