Hi Hoss,

 I don't have a query that reproduces it yet. The error is seen in
production logs only, and I cannot apply patches on those nodes. I will
keep looking for the query and will keep you updated.  Another bit of
extended exception trace is as follows -

Caused by: java.lang.IllegalArgumentException: Comparison method violates
its general contract!\n\tat java.util.TimSort.mergeHi(TimSort.java:903)
~[?:?]\n\tat java.util.TimSort.mergeAt(TimSort.java:520) ~[?:?]\n\tat
java.util.TimSort.mergeForceCollapse(TimSort.java:461) ~[?:?]\n\tat
java.util.TimSort.sort(TimSort.java:254) ~[?:?]\n\tat
java.util.Arrays.sort(Arrays.java:1233) ~[?:?]\n\tat
org.apache.solr.ltr.LTRRescorer.rerank(LTRRescorer.java:141) ~[?:?]\n\tat
org.apache.solr.ltr.LTRRescorer.rescore(LTRRescorer.java:126) ~[?:?]\n\tat
org.apache.solr.search.ReRankCollector.topDocs(ReRankCollector.java:118)
~[?:?]\n\t... 61



On Mon, Nov 27, 2023 at 2:24 PM Chris Hostetter <hossman_luc...@fucit.org>
wrote:

>
> : LTR query throwing the following exception, what could be the reasons? It
> : is Solr 9.1.1
>
> It means there is a really bad bug in Solr that the JVM is complaining
> about, and your data just happens to hit it ... but at a glance I'm not
> seeing any obvious problem with the code.  (unless maybe the internal call
> to Float.compare() is returning Integer.MIN_VALUE and we're getting int
> rollover when it's negated?)
>
>
> Does this error reliably reproduce for you with a given query? with lots
> of queries?
>
> Are you familiar with how to build solr from source?  If i gave you a
> patch that added a bunch of debug logging, would you be able to recompile
> solr and try the same query against the same data and put the (very
> verbose) debug logging up on a pastebin somewhere for review?
>
>
>
> -Hoss
> http://www.lucidworks.com/
>

Reply via email to