uschindler commented on issue #15068:
URL: https://github.com/apache/lucene/issues/15068#issuecomment-3223066748

   Hi,
   
   > After investigating the production outage, you are absolutely correct that 
we were illegally using a searcher that had already been released. I found an 
error log with `AlreadyClosedException` thrown from an async thread just before 
the close thread enters the infinite loop. I will fix this usage.
   > 
   > It seems we did get rather unlucky here - rather than experiencing a 
runtime exception on one thread, we entered into a fatal state (infinite loop) 
which brought down our node (the spinning thread held a critical lock...).
   > 
   > Thanks for fixing this bug! I see 
[#15112](https://github.com/apache/lucene/pull/15112) already merged.
   
   Thanks for the confirmation!
   
   Regarding the severity of this bug see the linked PR- I gave a comment. The 
fix will be in Lucene 10.3 and Lucene 11 (main). If and only if we release a 
9.12.x version to fix bugs, we should really backport it there, too. But using 
setGrouping(NO_GROUPING) shoudl be as a workaround if you hit this, to allow 
better debugging. But the underlying problem is generally in user's code.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org

Reply via email to