FWIW, Failed PeerSync with debug log enabled left pretty odd exception in
the log
136672 DEBUG (qtp662266656-56) [ x:collection1] o.a.s.c.S.Request
[collection1] webapp= path=/get
params={getUpdates=6000...7001&distrib=false&qt=/get&fingerprint=true&onlyIfActive=false&wt=javabin&version=2}
136672 DEBUG (qtp662266656-56) [ x:collection1]
o.a.s.h.c.RealTimeGetComponent Error in solrcloud_debug block
=> java.lang.NullPointerException
at
org.apache.solr.handler.component.RealTimeGetComponent.process(RealTimeGetComponent.java:170)
java.lang.NullPointerException: null
at
org.apache.solr.handler.component.RealTimeGetComponent.process(RealTimeGetComponent.java:170)
~[main/:?]
Looking into code made me puzzled.
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
