You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Walter Underwood <wa...@gmail.com> on 2017/02/17 23:46:01 UTC
Replicas fail immediately in new collection
Any idea why I would be getting this on a brand new, empty collection on the first update?
<body><h2>HTTP ERROR 500</h2>
<p>Problem accessing /solr/tutors_shard1_replica9/update. Reason:
<pre> Server Error</pre></p><h3>Caused by:</h3><pre>java.lang.NoSuchMethodError: org.apache.solr.update.TransactionLog$LogCodec.writeStr(Ljava/lang/String;)V
at org.apache.solr.update.TransactionLog.writeCommit(TransactionLog.java:457)
wunder
Walter Underwood
wunder@wunderwood.org
http://observer.wunderwood.org/ (my blog)
Re: Replicas fail immediately in new collection
Posted by Walter Underwood <wu...@wunderwood.org>.
I finally figured this out yesterday. Because the jar files have the version in the file name, I had a mix of jars from different versions. Depending on the load order, Solr could get into a situation where it was calling something that didn’t exist.
That was mysterious.
wunder
Walter Underwood
wunder@wunderwood.org
http://observer.wunderwood.org/ (my blog)
> On Feb 23, 2017, at 6:55 AM, Shalin Shekhar Mangar <sh...@gmail.com> wrote:
>
> SOLR-9739 changed the writeStr method to accept a CharSequence from
> String in 6.4 so my guess is that your classpath has a newer (6.4+)
> solrj version but an older solr-core jar that cannot find this new
> method.
>
> On Sat, Feb 18, 2017 at 5:16 AM, Walter Underwood
> <wa...@gmail.com> wrote:
>> Any idea why I would be getting this on a brand new, empty collection on the first update?
>>
>> <body><h2>HTTP ERROR 500</h2>
>> <p>Problem accessing /solr/tutors_shard1_replica9/update. Reason:
>> <pre> Server Error</pre></p><h3>Caused by:</h3><pre>java.lang.NoSuchMethodError: org.apache.solr.update.TransactionLog$LogCodec.writeStr(Ljava/lang/String;)V
>> at org.apache.solr.update.TransactionLog.writeCommit(TransactionLog.java:457)
>>
>>
>> wunder
>> Walter Underwood
>> wunder@wunderwood.org
>> http://observer.wunderwood.org/ (my blog)
>>
>>
>
>
>
> --
> Regards,
> Shalin Shekhar Mangar.
Re: Replicas fail immediately in new collection
Posted by Shalin Shekhar Mangar <sh...@gmail.com>.
SOLR-9739 changed the writeStr method to accept a CharSequence from
String in 6.4 so my guess is that your classpath has a newer (6.4+)
solrj version but an older solr-core jar that cannot find this new
method.
On Sat, Feb 18, 2017 at 5:16 AM, Walter Underwood
<wa...@gmail.com> wrote:
> Any idea why I would be getting this on a brand new, empty collection on the first update?
>
> <body><h2>HTTP ERROR 500</h2>
> <p>Problem accessing /solr/tutors_shard1_replica9/update. Reason:
> <pre> Server Error</pre></p><h3>Caused by:</h3><pre>java.lang.NoSuchMethodError: org.apache.solr.update.TransactionLog$LogCodec.writeStr(Ljava/lang/String;)V
> at org.apache.solr.update.TransactionLog.writeCommit(TransactionLog.java:457)
>
>
> wunder
> Walter Underwood
> wunder@wunderwood.org
> http://observer.wunderwood.org/ (my blog)
>
>
--
Regards,
Shalin Shekhar Mangar.