Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
Reply-To: solr-user@lucene.apache.org
Received-SPF: neutral (nike.apache.org: 209.85.223.182 is neither permitted
 nor denied by domain of salman.akram@northbaysolutions.net)
MIME-Version: 1.0
From: Salman Akram <salman.akram@northbaysolutions.net>
Date: Tue, 9 Sep 2014 08:54:17 +0500
Message-ID: 
 <CAKQOKRquyRmjyW+1JPvwyOVEQwZGytKHEjmE43+cYNC=Cj=rQQ@mail.gmail.com>
Subject: Master - Master / Upgrading a slave to master
To: Solr Group <solr-user@lucene.apache.org>
Content-Type: multipart/alternative; boundary=089e0153835aee2be5050299e4c5

--089e0153835aee2be5050299e4c5
Content-Type: text/plain; charset=UTF-8

We have a redundant data center in case the primary goes down. Currently we
have 1 master and multiple slaves on primary data center. This master also
replicates to a slave in secondary data center. So if the primary goes down
at least the read only part works. However, now we want writes to work on
secondary data center too when primary goes down.

- Is it possible in SOLR to have Master - Master?
- If not then what's the best strategy to upgrade a slave to master?
- Naturally there would be some latency due to data centers being in
different geographical locations so what are the normal data issues and
best practices in case primary goes down? We would also like to shift back
to primary as soon as its back.


Thanks!

-- 
Regards,

Salman Akram

--089e0153835aee2be5050299e4c5--