day, June 20, 2007 11:43:02 PM
Subject: Re: Slave/Master swap
: The more expensive solution might be to have Solr instances run on top
: of a SAN and then one could really have multiple Master instances, one
: in stand-by mode and ready to be started as the new Master if the
i *believe* that if
Hostetter <[EMAIL PROTECTED]>
To: solr-user@lucene.apache.org
Sent: Wednesday, June 20, 2007 11:43:02 PM
Subject: Re: Slave/Master swap
: The more expensive solution might be to have Solr instances run on top
: of a SAN and then one could really have multiple Master instances, one
: in stand-b
: The more expensive solution might be to have Solr instances run on top
: of a SAN and then one could really have multiple Master instances, one
: in stand-by mode and ready to be started as the new Master if the
i *believe* that if you have two solr isntances pointed at the same
physical data
]>
To: solr-user@lucene.apache.org
Sent: Wednesday, June 20, 2007 9:40:51 PM
Subject: Re: Slave/Master swap
: I'm wondering if there are slicker ways to do this, ways that would
: minimize the downtime, for instance. Perhaps, just like Will Johnson is
: trying to make IndexSchema updateab
: I'm wondering if there are slicker ways to do this, ways that would
: minimize the downtime, for instance. Perhaps, just like Will Johnson is
: trying to make IndexSchema updateable in a live system, the snapshooter
: could be turned on/off programatically, say via a special request
: handler.
Hi,
I saw https://issues.apache.org/jira/browse/SOLR-265 (Make IndexSchema
updateable in live system) which made me think of something I wished for a
while back.
Having a single Solr Master and a couple of Solr Slaves is a common setup. If
any of the Slaves fails, a decent LB knows not to t
