Re: Replication Problem from solr-3.6 to solr-4.0

I did optimize the master and the slave started replicating the indices! -- View this message in context: http://lucene.472066.n3.nabble.com/Replication-Problem-from-solr-3-6-to-solr-4-0-tp4025028p4148953.html Sent from the Solr - User mailing list archive at Nabble.com.

Re: Replication Problem from solr-3.6 to solr-4.0

Same with me too, in a multi-core Master/Slave. 11:17:30.476 [snapPuller-8-thread-1] INFO o.a.s.h.SnapPuller - Master's generation: 87 11:17:30.476 [snapPuller-8-thread-1] INFO o.a.s.h.SnapPuller - Slave's generation: 3 11:17:30.476 [snapPuller-8-thread-1] INFO o.a.s.h.SnapPuller - Starting rep

Re: Replication Problem from solr-3.6 to solr-4.0

Hi, i am running into the exact same problem: 27534 [qtp989080272-12] INFO org.apache.solr.core.SolrCore – [collection1] webapp=/solr path=/replication params={command=details&_=1394164320017&wt=json} status=0 QTime=12 28906 [qtp989080272-12] INFO org.apache.solr.core.SolrCore – [collection1

Re: Replication problem on windows

Hello! Thanks for the answer Shawn. -- Regards, Rafał Kuć Sematext :: http://sematext.com/ :: Solr - Lucene - Nutch > On 2/6/2012 3:04 AM, Rafał Kuć wrote: >> Hello! >> >> We have Solr running on Windows. Once in a while we see a problem with >> replication failing. While slave server replic

Re: Replication problem on windows

On 2/6/2012 3:04 AM, Rafał Kuć wrote: Hello! We have Solr running on Windows. Once in a while we see a problem with replication failing. While slave server replicates the index, it throws exception like the following: SEVERE: Unable to copy index file from: D:\web\solr\collection\data\index.20

Re: Replication problem

Multiple replicateAfter for example: startup,optimize I believe this was causing the issue, I limited it to commit, and it started to work (with no other changes to solrconfig.xml) On Tue, Jan 12, 2010 at 11:24 AM, Yonik Seeley wrote: > On Tue, Jan 12, 2010 at 2:17 PM, Jason Rutherglen > wrote:

Re: Replication problem

On Tue, Jan 12, 2010 at 2:17 PM, Jason Rutherglen wrote: > It was having multiple replicateAfter values... Perhaps a bug, though > I probably won't spend time investigating the why right now, nor > reproducing in the test cases. Do you mean that you changed the config and now it's working? We hav

Re: Replication problem

It was having multiple replicateAfter values... Perhaps a bug, though I probably won't spend time investigating the why right now, nor reproducing in the test cases. On Tue, Jan 12, 2010 at 11:10 AM, Jason Rutherglen wrote: > Hmm...Even with the IP address in the master URL on the slave, the > in

Re: Replication problem

Hmm...Even with the IP address in the master URL on the slave, the indexversion command to the master mysteriously doesn't show the latest commit... Totally freakin' bizarre! On Tue, Jan 12, 2010 at 10:53 AM, Jason Rutherglen wrote: > There's a connect exception on the client, however I'd expect

Re: Replication problem

There's a connect exception on the client, however I'd expect this to show up in the slave replication console (it's not). Is this correct behavior (i.e. not showing replication errors)? On Mon, Jan 11, 2010 at 9:50 AM, Jason Rutherglen wrote: > Yonik, > > I added startup to replicateAfter, howe

Re: Replication problem

Yonik, I added startup to replicateAfter, however no dice... There's no errors the Tomcat log. The output of: http://localhost-master:8080/solr/main/replication?command=indexversion 0 0 0 0 The master replication UI: Local Index Index Version: 1263182366335, Generation: 3 Locati

Re: Replication problem

Did you try adding "startup" to the list of events to replicate after? -Yonik http://www.lucidimagination.com On Mon, Jan 11, 2010 at 12:25 PM, Jason Rutherglen wrote: > Hi, sorry for the somewhat inane question: > > I setup replication request handler on the master however I'm not > seeing any