You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by Jeff Newburn <jn...@zappos.com> on 2009/03/03 00:00:56 UTC
Re: Replication page failure :(
I have tracked down the error to the specific date and file. On 2009-02-13
changes were apparently made to fix the replication page for replication off
of a master and slave server. This causes the jasper error in the
replication/index.jsp file. I am not sure why it does as most of the file
was rewritten during that update. I have included the information on
revisions below.
Date: 2009-02-13
svn up -r {2009-02-13} src/webapp/web/admin/replication/index.jsp (This
breaks the page)
Updated to revision 744021
Items added into CHANGES.txt
-31. SOLR-1015: Incomplete information in replication admin page and http
command response when server
- is both master and slave i.e. when server is a repeater (Akshay Ukey
via shalin)
-32. SOLR-1018: Slave is unable to replicate when server acts as repeater
(as both master and slave)
- (Akshay Ukey, Noble Paul via shalin)
Any help would be appreciated.
--
Jeff Newburn
Software Engineer, Zappos.com
jnewburn@zappos.com - 702-943-7562
From: Jeff Newburn <jn...@zappos.com>
Date: Fri, 27 Feb 2009 10:46:13 -0800
To: "solr-dev@lucene.apache.org" <so...@lucene.apache.org>
Conversation: Replication page failure :(
Subject: Replication page failure :(
When updating to trunk for the code the replication page no longer works it
is a page of exception code.
Info:
Slave server on the replication page. Just a code dump as follows.
Feb 27, 2009 8:44:37 AM org.apache.solr.common.SolrException log
SEVERE: org.apache.jasper.JasperException: java.lang.NullPointerException
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:4
18)
at
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:337)
at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:290)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:206)
at
org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher.
java:630)
at
org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDis
patcher.java:436)
at
org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatch
er.java:374)
at
org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatcher
.java:302)
at
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:
273)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:235)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:206)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:233)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:175)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128
)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102
)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:109)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286)
at
org.apache.coyote.http11.Http11NioProcessor.process(Http11NioProcessor.java:
879)
at
org.apache.coyote.http11.Http11NioProtocol$Http11ConnectionHandler.process(H
ttp11NioProtocol.java:719)
at
org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:
2080)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.ja
va:885)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:9
07)
at java.lang.Thread.run(Thread.java:619)
Caused by: java.lang.NullPointerException
at
org.apache.jsp.admin.replication.index_jsp._jspService(index_jsp.java:294)
at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
at
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:3
74)
... 24 more
--
Jeff Newburn
Software Engineer, Zappos.com
jnewburn@zappos.com - 702-943-7562
Re: Replication page failure :(
Posted by Jeff Newburn <jn...@zappos.com>.
Below are the details for both master and slave. Even though they seem to
have the replicatableindexversion it is not showing on the admin replication
page.
Details for Master:
<lst name="details">
<str name="indexSize">671.95 MB</str>
<str name="indexPath">/opt/solr-data/zeta-main/index</str>
−
<arr name="commits">
−
<lst>
<long name="indexversion">1233423825702</long>
<long name="generation">4240</long>
−
<str name="filelist">
[_3z7.fdt, _3z7.prx, _3z7.fdx, _3zt.nrm, _3z7.tis, _3zs.prx, _3zs.nrm,
segments_39s, _3zt.fdx, _3zs.fdt, _3zt.fdt, _3zs.fdx, _3z7.nrm, _3zs.fnm,
_3z7.fnm, _3zt.tis, _3zt.tvx, _3zs.tvf, _3zt.frq, _3zs.tis, _3zs.tvd,
_3zt.tii, _3zs.frq, _3zs.tii, _3z7.tvx, _3zt.tvd, _3zt.prx, _3zs.tvx,
_3z7.tii, _3z7.tvf, _3zt.tvf, _3z7.tvd, _3z7.frq, _3zt.fnm, _3z7_j.del]
</str>
</lst>
</arr>
<str name="isMaster">true</str>
<str name="isSlave">false</str>
<long name="indexVersion">1233423825702</long>
<long name="generation">4240</long>
−
<lst name="master">
−
<str name="confFiles">
slave_solrconfig.xml:solrconfig.xml,schema.xml,stopwords.txt,elevate.xml,syn
onyms.txt
</str>
<str name="replicateAfter">commit, optimize</str>
<long name="replicatableIndexVersion">1233423825702</long>
<long name="replicatableGeneration">4240</long>
</lst>
</lst>
−
<str name="WARNING">
This response format is experimental. It is likely to change in the future.
</str>
XML for replication on a slave:
<lst name="details">
<str name="indexSize">671.95 MB</str>
<str name="indexPath">/opt/solr-data/zeta-main/index</str>
−
<arr name="commits">
−
<lst>
<long name="indexversion">1233423825702</long>
<long name="generation">4240</long>
−
<str name="filelist">
[_3z7.fdt, _3z7.prx, _3z7.fdx, _3zt.nrm, _3z7.tis, _3zs.prx, _3zs.nrm,
segments_39s, _3zt.fdx, _3zs.fdt, _3zt.fdt, _3zs.fdx, _3z7.nrm, _3zs.fnm,
_3z7.fnm, _3zt.tis, _3zt.tvx, _3zs.tvf, _3zt.frq, _3zs.tis, _3zs.tvd,
_3zt.tii, _3zs.frq, _3zs.tii, _3z7.tvx, _3zt.tvd, _3zt.prx, _3zs.tvx,
_3z7.tii, _3z7.tvf, _3zt.tvf, _3z7.tvd, _3z7.frq, _3zt.fnm, _3z7_j.del]
</str>
</lst>
</arr>
<str name="isMaster">false</str>
<str name="isSlave">true</str>
<long name="indexVersion">1233423825702</long>
<long name="generation">4240</long>
−
<lst name="slave">
−
<lst name="masterDetails">
<str name="indexSize">671.95 MB</str>
<str name="indexPath">/opt/solr-data/zeta-main/index</str>
−
<arr name="commits">
−
<lst>
<long name="indexversion">1233423825702</long>
<long name="generation">4240</long>
−
<str name="filelist">
[_3z7.fdt, _3z7.prx, _3z7.fdx, _3zt.nrm, _3z7.tis, _3zs.prx, _3zs.nrm,
segments_39s, _3zt.fdx, _3zs.fdt, _3zt.fdt, _3zs.fdx, _3z7.nrm, _3zs.fnm,
_3z7.fnm, _3zt.tis, _3zt.tvx, _3zs.tvf, _3zt.frq, _3zs.tis, _3zs.tvd,
_3zt.tii, _3zs.frq, _3zs.tii, _3z7.tvx, _3zt.tvd, _3zt.prx, _3zs.tvx,
_3z7.tii, _3z7.tvf, _3zt.tvf, _3z7.tvd, _3z7.frq, _3zt.fnm, _3z7_j.del]
</str>
</lst>
</arr>
<str name="isMaster">true</str>
<str name="isSlave">false</str>
<long name="indexVersion">1233423825702</long>
<long name="generation">4240</long>
−
<lst name="master">
−
<str name="confFiles">
slave_solrconfig.xml:solrconfig.xml,schema.xml,stopwords.txt,elevate.xml,syn
onyms.txt
</str>
<str name="replicateAfter">commit, optimize</str>
<long name="replicatableIndexVersion">1233423825702</long>
<long name="replicatableGeneration">4240</long>
</lst>
</lst>
−
<str name="masterUrl">
http://10.66.209.38:8080/solr/zeta-main/replication
</str>
<str name="pollInterval">00:05:00</str>
<str name="nextExecutionAt">Tue Mar 10 09:51:32 PDT 2009</str>
<str name="indexReplicatedAt">Tue Mar 10 09:46:32 PDT 2009</str>
<str name="timesIndexReplicated">2447</str>
<str name="confFilesReplicated"/>
<str name="timesConfigReplicated"/>
<str name="confFilesReplicatedAt"/>
<str name="filesToDownload">[]</str>
<str name="numFilesToDownload">0</str>
<str name="bytesToDownload">0 bytes</str>
<str name="filesDownloaded">[]</str>
<str name="numFilesDownloaded">0</str>
<str name="timeElapsed">0s</str>
<str name="currentFile">_3z7_j.del</str>
<str name="currentFileSize">64 bytes</str>
<str name="currentFileSizeDownloaded">0 bytes</str>
<str name="currentFileSizePercent">0.0</str>
<str name="bytesDownloaded">0 bytes</str>
<str name="totalPercent">0.0</str>
<str name="timeRemaining">0s</str>
<str name="downloadSpeed">0 bytes</str>
<str name="isPollingDisabled">false</str>
<str name="isReplicating">false</str>
</lst>
</lst>
−
<str name="WARNING">
This response format is experimental. It is likely to change in the future.
</str>
--
Jeff
Newburn
Software Engineer, Zappos.com
jnewburn@zappos.com - 702-943-7562
> From: Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>
> Reply-To: <so...@lucene.apache.org>
> Date: Tue, 10 Mar 2009 10:07:18 +0530
> To: <so...@lucene.apache.org>
> Subject: Re: Replication page failure :(
>
> can you just paste the output of the details command on the master . I
> could help debug
>
> On Tue, Mar 10, 2009 at 2:25 AM, Jeff Newburn <jn...@zappos.com> wrote:
>> The command shows the data available on both the master and slave servers.
>> However, the actual replication page does not show any replicatable index
>> version.
>>
>> --
>> Jeff Newburn
>> Software Engineer, Zappos.com
>> jnewburn@zappos.com - 702-943-7562
>>
>>
>>> From: Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>
>>> Reply-To: <so...@lucene.apache.org>
>>> Date: Tue, 10 Mar 2009 00:22:38 +0530
>>> To: <so...@lucene.apache.org>
>>> Subject: Re: Replication page failure :(
>>>
>>> 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-0e25211b6ef50373fcc2f9a6ad4
>>> 03
>>> 80c169a5397
>>>
>>>
>>> On Mon, Mar 9, 2009 at 11:42 PM, Jeff Newburn <jn...@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
>>>> jnewburn@zappos.com - 702-943-7562
>>>>
>>>>
>>>>> From: Shalin Shekhar Mangar <sh...@gmail.com>
>>>>> Reply-To: <so...@lucene.apache.org>
>>>>> Date: Sat, 7 Mar 2009 01:11:52 +0530
>>>>> To: <so...@lucene.apache.org>
>>>>> Subject: Re: Replication page failure :(
>>>>>
>>>>> On Wed, Mar 4, 2009 at 9:19 PM, Jeff Newburn <jn...@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
>>
>>
>
>
>
> --
> --Noble Paul
Re: Replication page failure :(
Posted by Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>.
can you just paste the output of the details command on the master . I
could help debug
On Tue, Mar 10, 2009 at 2:25 AM, Jeff Newburn <jn...@zappos.com> wrote:
> The command shows the data available on both the master and slave servers.
> However, the actual replication page does not show any replicatable index
> version.
>
> --
> Jeff Newburn
> Software Engineer, Zappos.com
> jnewburn@zappos.com - 702-943-7562
>
>
>> From: Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>
>> Reply-To: <so...@lucene.apache.org>
>> Date: Tue, 10 Mar 2009 00:22:38 +0530
>> To: <so...@lucene.apache.org>
>> Subject: Re: Replication page failure :(
>>
>> 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-0e25211b6ef50373fcc2f9a6ad403
>> 80c169a5397
>>
>>
>> On Mon, Mar 9, 2009 at 11:42 PM, Jeff Newburn <jn...@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
>>> jnewburn@zappos.com - 702-943-7562
>>>
>>>
>>>> From: Shalin Shekhar Mangar <sh...@gmail.com>
>>>> Reply-To: <so...@lucene.apache.org>
>>>> Date: Sat, 7 Mar 2009 01:11:52 +0530
>>>> To: <so...@lucene.apache.org>
>>>> Subject: Re: Replication page failure :(
>>>>
>>>> On Wed, Mar 4, 2009 at 9:19 PM, Jeff Newburn <jn...@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
>
>
--
--Noble Paul
Re: Replication page failure :(
Posted by Jeff Newburn <jn...@zappos.com>.
The command shows the data available on both the master and slave servers.
However, the actual replication page does not show any replicatable index
version.
--
Jeff Newburn
Software Engineer, Zappos.com
jnewburn@zappos.com - 702-943-7562
> From: Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>
> Reply-To: <so...@lucene.apache.org>
> Date: Tue, 10 Mar 2009 00:22:38 +0530
> To: <so...@lucene.apache.org>
> Subject: Re: Replication page failure :(
>
> 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-0e25211b6ef50373fcc2f9a6ad403
> 80c169a5397
>
>
> On Mon, Mar 9, 2009 at 11:42 PM, Jeff Newburn <jn...@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
>> jnewburn@zappos.com - 702-943-7562
>>
>>
>>> From: Shalin Shekhar Mangar <sh...@gmail.com>
>>> Reply-To: <so...@lucene.apache.org>
>>> Date: Sat, 7 Mar 2009 01:11:52 +0530
>>> To: <so...@lucene.apache.org>
>>> Subject: Re: Replication page failure :(
>>>
>>> On Wed, Mar 4, 2009 at 9:19 PM, Jeff Newburn <jn...@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
Re: Replication page failure :(
Posted by Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>.
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 <jn...@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
> jnewburn@zappos.com - 702-943-7562
>
>
>> From: Shalin Shekhar Mangar <sh...@gmail.com>
>> Reply-To: <so...@lucene.apache.org>
>> Date: Sat, 7 Mar 2009 01:11:52 +0530
>> To: <so...@lucene.apache.org>
>> Subject: Re: Replication page failure :(
>>
>> On Wed, Mar 4, 2009 at 9:19 PM, Jeff Newburn <jn...@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
Re: Replication page failure :(
Posted by Jeff Newburn <jn...@zappos.com>.
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
jnewburn@zappos.com - 702-943-7562
> From: Shalin Shekhar Mangar <sh...@gmail.com>
> Reply-To: <so...@lucene.apache.org>
> Date: Sat, 7 Mar 2009 01:11:52 +0530
> To: <so...@lucene.apache.org>
> Subject: Re: Replication page failure :(
>
> On Wed, Mar 4, 2009 at 9:19 PM, Jeff Newburn <jn...@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.
Re: Replication page failure :(
Posted by Shalin Shekhar Mangar <sh...@gmail.com>.
On Wed, Mar 4, 2009 at 9:19 PM, Jeff Newburn <jn...@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.
Re: Replication page failure :(
Posted by Jeff Newburn <jn...@zappos.com>.
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)
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.
--
Jeff Newburn
Software Engineer, Zappos.com
jnewburn@zappos.com - 702-943-7562
> From: Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>
> Reply-To: <so...@lucene.apache.org>
> Date: Wed, 4 Mar 2009 10:08:26 +0530
> To: <so...@lucene.apache.org>
> Subject: Re: Replication page failure :(
>
> Hi jeff ,
>
> we were unable to reproduce the issue with the current trunk. Could
> you please confirmthat this error happens with the latest nightly
> also?
>
>
> On Wed, Mar 4, 2009 at 9:57 AM, Chris Hostetter
> <ho...@fucit.org> wrote:
>>
>> : I have tracked down the error to the specific date and file. On 2009-02-13
>> : changes were apparently made to fix the replication page for replication
>> off
>> : of a master and slave server. This causes the jasper error in the
>> : replication/index.jsp file. I am not sure why it does as most of the file
>> : was rewritten during that update. I have included the information on
>> : revisions below.
>>
>> i'm not very familiar with the java replication, but can you let us
>> know how you have the replication handler configured -- that might help
>> identify a code path that is resulting in this NPE.
>>
>>
>> : Caused by: java.lang.NullPointerException
>> : at
>> : org.apache.jsp.admin.replication.index_jsp._jspService(index_jsp.java:294)
>> : at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
>> : at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
>> : at
>>
>>
>>
>>
>> -Hoss
>>
>>
>
>
>
> --
> --Noble Paul
Re: Replication page failure :(
Posted by Noble Paul നോബിള് नोब्ळ् <no...@gmail.com>.
Hi jeff ,
we were unable to reproduce the issue with the current trunk. Could
you please confirmthat this error happens with the latest nightly
also?
On Wed, Mar 4, 2009 at 9:57 AM, Chris Hostetter
<ho...@fucit.org> wrote:
>
> : I have tracked down the error to the specific date and file. On 2009-02-13
> : changes were apparently made to fix the replication page for replication off
> : of a master and slave server. This causes the jasper error in the
> : replication/index.jsp file. I am not sure why it does as most of the file
> : was rewritten during that update. I have included the information on
> : revisions below.
>
> i'm not very familiar with the java replication, but can you let us
> know how you have the replication handler configured -- that might help
> identify a code path that is resulting in this NPE.
>
>
> : Caused by: java.lang.NullPointerException
> : at
> : org.apache.jsp.admin.replication.index_jsp._jspService(index_jsp.java:294)
> : at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
> : at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
> : at
>
>
>
>
> -Hoss
>
>
--
--Noble Paul
Re: Replication page failure :(
Posted by Chris Hostetter <ho...@fucit.org>.
: I have tracked down the error to the specific date and file. On 2009-02-13
: changes were apparently made to fix the replication page for replication off
: of a master and slave server. This causes the jasper error in the
: replication/index.jsp file. I am not sure why it does as most of the file
: was rewritten during that update. I have included the information on
: revisions below.
i'm not very familiar with the java replication, but can you let us
know how you have the replication handler configured -- that might help
identify a code path that is resulting in this NPE.
: Caused by: java.lang.NullPointerException
: at
: org.apache.jsp.admin.replication.index_jsp._jspService(index_jsp.java:294)
: at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
: at javax.servlet.http.HttpServlet.service(HttpServlet.java:803)
: at
-Hoss