We are running two Solr servers (master/slave) on EC2 and have the solr home
directories on EBS drives that we snapshot every 12 hours. While that will
mean that we will lose at most 12 hours of data, I wondered if there was a way
I could reduce the window of data loss. With our mysql servers
ectory? That's the heart of
> the Lucene index there. Look at Solr's admin, it'll tell you the data
> directory location it is using, be sure it is set where you think it should
> be.
>
> Erik
>
> On Jan 24, 2010, at 8:59 AM, athir nuaimi wrote:
>
We have a working system based on Solr 1.3 that I tried to upgrade to 1.4 with
no luck. The new 1.4 Solr server is up and running but always returns 0
results when you query it. It seems to have the correct schema but the number
of documents is 0 even though I used a backup of the production d
I have a master and slave setup for solr. The slave gets updates by using
snappuller and then snapinstaller.The installer reports that is takes about
75 seconds to install the new index. During that time, are (web) clients able
to do queries to the slave? If not, is that a strategy that
We have 4 machines running solr. On one of the machines, every 2-3
days solr stops running. By that I mean that the java/tomcat
process just disappears. If I look at the catalina logs, I see
normal log entries and then nothing. There is no shutdown messages
like you would normally see i
