Or ...
1. Promote existing slave to new master
2. Add new slave to cluster
-Bryan
On May 13, 2009, at May 13, 9:48 AM, Jay Hill wrote:
- Migrate configuration files from old master (or backup) to new
master.
- Replicate from a slave to the new master.
- Resume indexing to new master.
-Jay
On Wed, May 13, 2009 at 4:26 AM, nk 11 <nick.cass...@gmail.com> wrote:
Nice.
What if the master fails permanently (like a disk crash...) and the
new
master is a clean machine?
2009/5/13 Noble Paul നോബിള് नोब्ळ्
<noble.p...@corp.aol.com>
On Wed, May 13, 2009 at 12:10 PM, nk 11 <nick.cass...@gmail.com>
wrote:
Hello
I'm kind of new to Solr and I've read about replication, and the
fact
that a
node can act as both master and slave.
I a replica fails and then comes back on line I suppose that it
will
resyncs
with the master.
right
But what happnes if the master fails? A slave that is configured as
master
will kick in? What if that slave is not yes fully sync'ed with the
failed
master and has old data?
if the master fails you can't index the data. but the slaves will
continue serving the requests with the last index. You an bring back
the master up and resume indexing.
What happens when the original master comes back on line? He will
remain
a
slave because there is another node with the master role?
Thank you!
--
-----------------------------------------------------
Noble Paul | Principal Engineer| AOL | http://aol.com
