uschindler commented on PR #15112: URL: https://github.com/apache/lucene/pull/15112#issuecomment-3223057460
Hi @ayinresh, the fix was already backported to Lucene 10.3 which will come out soon. I don't think we'll release a 10.2.x bugfix variant, as we generally would only do this for major branches. If (and only if) we release another 9.12.x we can for sure include this bugfix, as it is serious for affected people (hangs completely with spinning CPU). About the "severity" of the bug: Yes, indeed it is severe, but only if your code is already broken. In Lucene 9 with older Java versions before 19 borken code using IndexReaders while it is closed would have been crushed the whole JVM, as we forcefully unmap the direct ByteBuffers - leading to a SIGSEGV. I think this is also the reason why we see only few people hit this bug. In one year this was the only encounter of this bug reported. So my opinion: It is not so serious for correctly written code. If your code is broken you may hang instead of getting correct AlreadyCloseExceptions. There is always a workaround: set MMapDirectory.setGrouping(NO_GROUPING) which restores the older 9.x behaviour. -- 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
