Jakov:
Be particularly aware of the ADDREPLICA collections API
command here:
https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api_addreplica
That allows you to specify exactly which node the new replica should be on,
so you can force it to be on the new HW. Here's a
I think ZK stuff may actually be easier to handle, no?
Add new ones to the existing ZK cluster and then remove the old ones.
Won't this work smoothly?
Otis
--
Monitoring * Alerting * Anomaly Detection * Centralized Log Management
Solr & Elasticsearch Support * http://sematext.com/
On Thu, Oct 30
On 10/30/2014 04:47 AM, Otis Gospodnetic wrote:
Hi/Bok Jakov,
2) sounds good to me. It means no down-time. 1) means stoppage. If
stoppage is not OK, but falling behind with indexing new content is OK, you
could:
* add a new cluster
* start reading from old index and indexing into the new inde
Hi/Bok Jakov,
2) sounds good to me. It means no down-time. 1) means stoppage. If
stoppage is not OK, but falling behind with indexing new content is OK, you
could:
* add a new cluster
* start reading from old index and indexing into the new index
* stop old cluster when done
* index new content
