can u hit the master ReplicationHandler with the command details and see if the info is available?
or u can just paste it here http://wiki.apache.org/solr/SolrReplication#head-0e25211b6ef50373fcc2f9a6ad40380c169a5397 On Mon, Mar 9, 2009 at 11:42 PM, Jeff Newburn <jnewb...@zappos.com> wrote: > It looks like it fixes the repliation error but the page still does not have > a Replicatable Index Version. It appears the master no longer sends that > back to the slave. > -- > Jeff Newburn > Software Engineer, Zappos.com > jnewb...@zappos.com - 702-943-7562 > > >> From: Shalin Shekhar Mangar <shalinman...@gmail.com> >> Reply-To: <solr-dev@lucene.apache.org> >> Date: Sat, 7 Mar 2009 01:11:52 +0530 >> To: <solr-dev@lucene.apache.org> >> Subject: Re: Replication page failure :( >> >> On Wed, Mar 4, 2009 at 9:19 PM, Jeff Newburn <jnewb...@zappos.com> wrote: >> >>> I was able to nail down what happened. Apparently, the update made a >>> change >>> in the xml returned from the master solr for replication. The page blows >>> up >>> due to "indexversion" changing to "indexVersion". So unless both master >>> and >>> server are at the revision it will blow up with a NPE. This is because >>> null >>> is cast to a Long then converted to a long primitive with no exception >>> handling. (index.jsp like 247) >> >> >> Can you try the SOLR-1050 patch? I think it should fix this problem. >> >> >>> After fixing the issue by upgrading master and slave I have noticed there >>> is >>> no Replicatable index version numbers. I looked at the return from the >>> master and it would appear there is nothing with those variables being >>> returned. We are currently using trunk as of 03/03/2009. Simple master to >>> many slaves relationship. >>> >> >> Do you mean that the replicatable index version is not being displayed? Or >> do you mean that replication is not happening at all? >> >> -- >> Regards, >> Shalin Shekhar Mangar. > > -- --Noble Paul
