Right, if there's no "fixed version" mentioned and if the resolution is "unresolved", it's not in the code base at all. But that JIRA is not apparently reproducible, especially on more recent versions that 6.2. Is it possible to test a more recent version (6.6.2 would be my recommendation).
Erick On Tue, Nov 21, 2017 at 9:58 PM, S G <sg.online.em...@gmail.com> wrote: > My bad. I found it at https://issues.apache.org/jira/browse/SOLR-9453 > But I could not find it in changes.txt perhaps because its yet not resolved. > > On Tue, Nov 21, 2017 at 9:15 AM, Erick Erickson <erickerick...@gmail.com> > wrote: > >> Did you check the JIRA list? Or CHANGES.txt in more recent versions? >> >> On Tue, Nov 21, 2017 at 1:13 AM, S G <sg.online.em...@gmail.com> wrote: >> > Hi, >> > >> > We are running 6.2 version of Solr and hitting this error frequently. >> > >> > Error while trying to recover. core=my_core:java.lang. >> NullPointerException >> > at org.apache.solr.update.PeerSync.handleUpdates( >> PeerSync.java:605) >> > at org.apache.solr.update.PeerSync.handleResponse( >> PeerSync.java:344) >> > at org.apache.solr.update.PeerSync.sync(PeerSync.java:257) >> > at org.apache.solr.cloud.RecoveryStrategy.doRecovery( >> RecoveryStrategy.java:376) >> > at org.apache.solr.cloud.RecoveryStrategy.run( >> RecoveryStrategy.java:221) >> > at java.util.concurrent.Executors$RunnableAdapter. >> call(Executors.java:511) >> > at java.util.concurrent.FutureTask.run(FutureTask.java:266) >> > at org.apache.solr.common.util.ExecutorUtil$ >> MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:229) >> > at java.util.concurrent.ThreadPoolExecutor.runWorker( >> ThreadPoolExecutor.java:1142) >> > at java.util.concurrent.ThreadPoolExecutor$Worker.run( >> ThreadPoolExecutor.java:617) >> > at java.lang.Thread.run(Thread.java:745) >> > >> > >> > >> > Is this a known issue and fixed in some newer version? >> > >> > >> > Thanks >> > SG >>
