jpountz commented on issue #13478:
URL: https://github.com/apache/lucene/issues/13478#issuecomment-2173545613
Disabling concurrent merging for terms, norms and doc values until we
figure out how to make it compatible with SortingCodecReader sounds good to me.
--
This is an automated mess
benwtrent commented on issue #13478:
URL: https://github.com/apache/lucene/issues/13478#issuecomment-2160939426
>Parallel merging breaks these assumptions and could cause issues.
Well, the assumptions are that its only accessed once. But now in parallel
merging, it could be re-cached
benwtrent commented on issue #13478:
URL: https://github.com/apache/lucene/issues/13478#issuecomment-2160815181
I think I know the issue with the parallel merging. This only happens when
we use a SortingCodecReader.
The key issue is here:
https://github.com/apache/lucene/commit/17c2
benwtrent commented on issue #13478:
URL: https://github.com/apache/lucene/issues/13478#issuecomment-2160620126
OK, the NPE in sort, I did some manual debugging via good ole
`System.out.println`. This only happens in the assertion if the cache check is
greater than 1, which does seem to hap
benwtrent opened a new issue, #13478:
URL: https://github.com/apache/lucene/issues/13478
### Description
It was noticed that the CMS intra-merge behavior was not fully tested. In an
effort to do this, a change to override when the intra-merge scheduler is used
has been drafted. https
