Some good points brought up in the discussion. The implementation we have
reindexes a shard reading all documents onto itself, but takes care of the
fact that no older version segment merges with a fresh segment.
This happens with zero downtime and without requiring a large storage
buffer. By the e
>> the only thing that makes sense is reindexing from source to a new
>> cluster that will replace the old cluster
Ideally yes, but there is a social aspect when Solr is managed as a
service and the many sources are opaque to the team managing it.
Let's assume for the sake of argument that the bel
