[prev in list] [next in list] [prev in thread] [next in thread] 

List:       solr-user
Subject:    Re: Migrating cloud to another set of machines
From:       Erick Erickson <erickerickson () gmail ! com>
Date:       2014-10-31 0:14:08
Message-ID: CAN4YXvemXTbjdYOhoQsZOQK-9pn_BhVMs=HBrcBWK1hkiX+NZw () mail ! gmail ! com
[Download RAW message or body]

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 guide:

http://heliosearch.org/solrcloud-assigning-nodes-machines/

Best,
Erick

On Thu, Oct 30, 2014 at 3:40 PM, Otis Gospodnetic
<otis.gospodnetic@gmail.com> wrote:
> 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, 2014 at 1:16 PM, Jakov Sosic <jsosic@gmail.com> wrote:
>
>> 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 index
>>> * stop old cluster when done
>>> * index new content to new cluster (or maybe you can be doing this all
>>> along if indexing old + new at the same time is OK for you)
>>> --
>>>
>>
>> Thank you for suggestions Otis.
>>
>> Everything is acceptable currently, but in the future as the data grows,
>> we will certainly enter those edge cases where neither stopping indexing
>> nor stopping queries will be acceptable.
>>
>> What makes things a little bit more problematic is that ZooKeepers are
>> migrating also to new machines.
>>
>>
>>
[prev in list] [next in list] [prev in thread] [next in thread]