Hello, Erick.
I've looked at one failed job
https://builds.apache.org/job/Lucene-Solr-Tests-8.x/183/consoleFull
It seems like severe serverside problem: it hangs for waiting for
"dependent" updates. It pass on my laptop, so far.
[junit4] 2> 2825663 INFO (qtp2139807079-27393) [
x:collection1] o.a.s.u.p.LogUpdateProcessorFactory [collection1]
webapp= path=/update
params={update.distrib=FROMLEADER&distrib.inplace.prevversion=6000&wt=javabin&version=2}{}
0 135571
[junit4] 2> 2825663 ERROR (qtp2139807079-27393) [
x:collection1] o.a.s.h.RequestHandlerBase java.lang.RuntimeException:
java.lang.InterruptedException
[junit4] 2> at
org.apache.solr.update.VersionBucket.awaitNanos(VersionBucket.java:68)
[junit4] 2> at
org.apache.solr.update.processor.DistributedUpdateProcessor.doWaitForDependentUpdates(DistributedUpdateProcessor.java:593)
[junit4] 2> at
org.apache.solr.update.processor.DistributedUpdateProcessor.lambda$waitForDependentUpdates$1(DistributedUpdateProcessor.java:536)
[junit4] 2> at
org.apache.solr.update.VersionBucket.runWithLock(VersionBucket.java:50)
[junit4] 2> at
org.apache.solr.update.processor.DistributedUpdateProcessor.waitForDependentUpdates(DistributedUpdateProcessor.java:536)
[junit4] 2> at
org.apache.solr.update.processor.DistributedUpdateProcessor.versionAdd(DistributedUpdateProcessor.java:327)
[junit4] 2> at
org.apache.solr.update.processor.DistributedUpdateProcessor.processAdd(DistributedUpdateProcessor.java:223)
[junit4] 2> at
org.apache.solr.update.processor.LogUpdateProcessorFactory$LogUpdateProcessor.processAdd(LogUpdateProcessorFactory.java:103)
[junit4] 2> at
org.apache.solr.handler.loader.JavabinLoader$1.update(JavabinLoader.java:110)
On Thu, May 2, 2019 at 3:14 AM Erick Erickson <[email protected]>
wrote:
> Are failing a lot with:
>
> Error Message:
> Unexpected exception type, expected SolrException but got
> org.apache.solr.client.solrj.SolrServerException: Timeout occurred while
> waiting response from
>
> Anyone working on this? The super-simple change would be to expect a
> different error, is that OK? I’m assuming that all that’s happening is a
> different error is being thrown due to some changes on the server side, but
> haven’t tried to track down whether that’s the issue or whether it’s deeper
> than that.
>
> Erick
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
--
Sincerely yours
Mikhail Khludnev
