Re: Master-Slave setup using SolrCloud

Apparently, there is a bug in Solr 4.10.0 which was causing the NullPointerExceptions. SOLR-6501 We have updated our production SOLR to 4.10.1 On Thu, Oct 2, 2014 at 8:13 PM, Sachin Kale wrote: > If I look into the logs, many times I get only fo

Re: Master-Slave setup using SolrCloud

If I look into the logs, many times I get only following line without any stacktrace: *ERROR - 2014-10-02 19:35:25.516; org.apache.solr.common.SolrException; java.lang.NullPointerException* These exceptions are not coming continuously. Once in every 10-15 minutes. But once it starts, there are co

Re: Master-Slave setup using SolrCloud

On 10/2/2014 6:58 AM, Sachin Kale wrote: > We are trying to move our traditional master-slave Solr configuration to > SolrCloud. As our index size is very small (around 1 GB), we are having > only one shard. > So basically, we are having same master-slave configuration with one leader > and 6 repli

Re: Master / slave setup with multicore

Ah, wait, my fault - I didn't have the right Solr port configured in the slave, so snapinstaller was commiting the master :/ Thanks, James On 2 May 2008, at 09:17, Bill Au wrote: snapinstall calls commit to trigger Solr to use the new index. Do you see the commit request in your Solr log?

Re: Master / slave setup with multicore

snapinstall calls commit to trigger Solr to use the new index. Do you see the commit request in your Solr log? Anything in the snapinstaller log? Bill On Thu, May 1, 2008 at 8:35 PM, James Brady <[EMAIL PROTECTED]> wrote: > Hi Ryan, thanks for that! > > I have one outstanding question: when I

Re: Master / slave setup with multicore

Hi Ryan, thanks for that! I have one outstanding question: when I take a snapshot on the master, snappull and snapinstall on the slave, the new index is not being used: restarting the slave server does pick up the changes, however. Has anyone else had this problem with recent development bu

Re: Master / slave setup with multicore

On Apr 29, 2008, at 3:09 PM, James Brady wrote: Hi all, I'm aiming to use the new multicore features in development versions of Solr. My ideal setup would be to have master / slave servers on the same machine, snapshotting across from the 'write' to the 'read' server at intervals. This w

Re: Master/Slave setup

ene - Solr - Nutch - Original Message > From: Walter Underwood <[EMAIL PROTECTED]> > To: solr-user@lucene.apache.org > Sent: Friday, February 29, 2008 2:36:12 PM > Subject: Re: Master/Slave setup > > In solrconfig.xml, configure a listener for "postOpt

Re: Master/Slave setup

uld write to some file after optimize is done (index version) > on the master, > and modify snappuller to look at that file... but it would be good if that > happens "out of the box" > > Thanks, > Alex > > > > ____ > &g

RE: Master/Slave setup

aster, and modify snappuller to look at that file... but it would be good if that happens "out of the box" Thanks, Alex From: Otis Gospodnetic [mailto:[EMAIL PROTECTED] Sent: Thu 2/28/2008 8:16 PM To: solr-user@lucene.apache.org Subject: Re: Mas

Re: Master/Slave setup

You have no cache at all when you stop and restart Solr. I recommend using the provided scripts for index distribution. Run snappuller and snapinstaller every two hours. The scripts already do the right thing. A snapshot is created after a commit on the indexer. Snappuller only copies over an inde

Re: Master/Slave setup

Alex, I think you should rethink the approach you described and reconsider using the provided replication scripts. - How often the searchers see the new index depends on how often the snappuller + snapinstaller are run on slaves. - If you want the searchers to get a new and optimized index ever