- Original Message
From: Rakesh Godhani [EMAIL PROTECTED]
To: solr-user@lucene.apache.org solr-user@lucene.apache.org
Sent: Monday, July 28, 2008 2:25:00 PM
Subject: Multiple Update servers
Hi, we are currently evaluating Solr and have been browsing the archives for
one particular issue
I use the snapshooter with rsync
2008/7/29 Rakesh Godhani [EMAIL PROTECTED]
After Matthew's comment I was thinking about putting them both behind a
load
balancer, with the LB directing all traffic to one until it fails and then
kick over to the other one.
In your architectures I'm guessing
Hi Rakesh,
Solr ships with a set of collection distribution scripts (rsync based) which
can be used to setup master-slave replication. I believe most people use
them for transferring index from master to slaves and use separate local
filesystems on their servers.
Take a look at
Thanks for the input, much appreciated.
-Rakesh
On 7/29/08 12:18 PM, Matthew Runo [EMAIL PROTECTED] wrote:
As far as I know only one machine can write to an index at a time.
More than that and I got corrupted indexes.
Thanks!
Matthew Runo
Software Developer
Zappos.com
702.943.7833
You could implement a script that woiuld control which master server is
indexing and put them behind something like a NAT.
I use that that control my master redundancy.
2008/7/29 Rakesh Godhani [EMAIL PROTECTED]
Thanks for the input, much appreciated.
-Rakesh
On 7/29/08 12:18 PM, Matthew
After Matthew's comment I was thinking about putting them both behind a load
balancer, with the LB directing all traffic to one until it fails and then
kick over to the other one.
In your architectures I'm guessing the masters share the same physical
index, but do the slaves share the same index
Hi, we are currently evaluating Solr and have been browsing the archives for
one particular issue but can¹t seem to find the answer, so please forgive me
if I¹m asking a repetitive question. We like the idea of having multiple
slave servers serving up queries and a master performing updates.
