Thanks Justin. We also temporarily fixed the deadlock.
If you have opened an issue, thank you very much for sharing it with us.
At 2022-04-25 00:39:00, "Justin Sweeney" wrote:
>Hi,
>
>We encountered a similar issue and fixed this in a patch on the fork of
>Solr we use. I can open an issue a
Thank you for your reply, we found the root cause.
It's our own fault.
At 2022-06-01 00:36:57, "Michael Gibney" wrote:
>`json.facet` covers a lot of ground and can do a lot of different
>things under the hood. Would you be able to share more specific
>information about the kinds of `
// update this sentence
"We found NumFound=2 when querying with debugQuery=true&q=id:1, and NumFound=1
when querying with debugQuery=true&q=id:2"
At 2022-06-11 23:58:59, "slly" wrote:
>Hello everyone.
> We recently upgraded the online version from Solr 7 to 8.11, we found a very
> stra
Thank you for your reply.
The _root_ field is defined as follows:
At 2022-06-12 00:05:00, "戴晓彬" wrote:
>check the managed-schema to see if the _root_ field is defined.
>
>> 2022年6月11日 23:58，slly 写道：
>>
>> Hello everyone.
>> We recently upgraded the online version from Solr 7 to
. The 8.x version
>will judge whether it is the same record according to _root_, so the update
>will become two after the upgrade.
>It is recommended to reindex after the upgrade.
>
>> 2022年6月12日 00:10，YangLiu 写道：
>>
>>
>>
>>
>> Tha
I think the problem is the same as this:
https://issues.apache.org/jira/browse/SOLR-16099
jetty's solution:
https://github.com/eclipse/jetty.project/issues/8558
At 2022-11-08 14:13:29, "slly" wrote:
>Hello everyone.
>
>
>We recently encountered an online problem, only restart the proce
Maybe this is a jdk “bug”, but it should be used incorrectly.
At 2023-01-04 19:58:35, "slly" wrote:
>Does anyone have similar problems?
>
>
>The cache class we configured is FastLRUCache in solrconfig.xml
>
>
>autowarmCount="0"/>
>
>
>Many threads are blocking the stack bel
he problem may be introduced by this change SOLR-1
At 2023-01-04 21:06:47, "YangLiu" wrote:
Maybe this is a jdk “bug”, but it should be used incorrectly.
At 2023-01-04 19:58:35, "slly" wrote:
>Does anyone have similar problems?
>
>
>The
