On 2/6/2014 4:00 AM, Shawn Heisey wrote:
I would not recommend it, but if you know for sure that your
infrastructure can handle it, then you should be able to optimize them
all at once by sending parallel optimize requests with distrib=false
directly to the Solr cores that hold the shard replicas, not the collection.
Followup on this thread:
Evidence now suggests (thank you, Yago!) that sending an optimize
request with distrib="false" might *NOT* optimize just the core that
receives the request. I can confirm that this is the case on a
SolrCloud 4.2.1 setup with one shard and replicationFactor=2. It
optimized that core, then when that was finished, optimized the other
replica.
I would have already filed an issue in Jira, except that I do not
currently have any way to test this on 4.6.1, so I do not know if this
is still the way it works. Also, I do not have a distributed SolrCloud
index available. I will be looking into writing a unit test, but my
grasp of SolrCloud tests is very weak.
Thanks,
Shawn
