Hi Andrzej,

Yes this is a breakage on branch_10x since the Lucene 10.4 upgrade. I ran
some analysis by rolling back branch_10x to lucene 10.3.2 and will share
the same later today for us to consider the options with 10.1.

Will also open a JIRA for the cuvs breakage for tracking.

Thanks,

Rahul

On Mon, Oct 12, 2026 at 3:49 AM Andrzej Bialecki <[email protected]> wrote:

> Hmm, that’s unfortunate indeed! :(
>
> However, I suspect it’s broken also on branch_10x (can you please verify?)
> because AFAIK branch_10_1 didn’t change these dependencies.
>
> If that’s the case then the choice is between withholding 10.1 for 2-3
> months more, when it’s already been 9 months since 10.0 - OR releasing 10.1
> with broken cuvs support now and then doing 10.2 in 2-3 months.
>
> I’m inclined towards releasing now, unfortunately with a known bug but
> still being a massive improvement over 10.0.
>
> What do you all think?
>
> Cheers,
> Andrzej
>
> On 2026/10/11 21:08:02 Rahul Goswami wrote:
> > Tried the RC. The cuvs module seems to be broken. Indexing fails on a GPU
> > enabled machine due to API incompatibility between cuvs-lucene and Lucene
> > 10.4.
> > Currently no available compatible cuvs-lucene version exists for Lucene
> > 10.4 and is expected to be available by December this year.
> >
> > If there is agreement, I could spend the effort on rolling Solr back to
> > Lucene 10.3.2 where I have validated cuvs to work (which was also the
> > Lucene version we were on prior to 10.4).
> >
> > Thoughts?
> >
> > 2026-10-10 20:57:58.804 WARN  (qtp166454155-71) []
> o.e.j.e.s.ServletChannel
> > /solr/vectors/update
> > *java.lang.NoSuchMethodError: 'int[]
> >
> org.apache.lucene.util.hnsw.HnswGraph$NodesIterator.getSortedNodes(org.apache.lucene.util.hnsw.HnswGraph$NodesIterator)'*
> > at
> >
> com.nvidia.cuvs.lucene.Lucene99AcceleratedHNSWVectorsWriter.writeGraph(Lucene99AcceleratedHNSWVectorsWriter.java:444)
> > at
> >
> com.nvidia.cuvs.lucene.Lucene99AcceleratedHNSWVectorsWriter.writeFieldInternal(Lucene99AcceleratedHNSWVectorsWriter.java:230)
> > at
> >
> com.nvidia.cuvs.lucene.Lucene99AcceleratedHNSWVectorsWriter.writeField(Lucene99AcceleratedHNSWVectorsWriter.java:502)
> > at
> >
> com.nvidia.cuvs.lucene.Lucene99AcceleratedHNSWVectorsWriter.flush(Lucene99AcceleratedHNSWVectorsWriter.java:494)
> > at
> >
> org.apache.lucene.codecs.perfield.PerFieldKnnVectorsFormat$FieldsWriter.flush(PerFieldKnnVectorsFormat.java:120)
> > at
> >
> org.apache.lucene.index.VectorValuesConsumer.flush(VectorValuesConsumer.java:76)
> > at org.apache.lucene.index.IndexingChain.flush(IndexingChain.java:305)
> > at
> >
> org.apache.lucene.index.DocumentsWriterPerThread.flush(DocumentsWriterPerThread.java:456)
> > at
> org.apache.lucene.index.DocumentsWriter.doFlush(DocumentsWriter.java:502)
> > at
> >
> org.apache.lucene.index.DocumentsWriter.maybeFlush(DocumentsWriter.java:456)
> > at
> >
> org.apache.lucene.index.DocumentsWriter.flushAllThreads(DocumentsWriter.java:649)
> > at
> >
> org.apache.lucene.index.IndexWriter.prepareCommitInternal(IndexWriter.java:3712)
> > at
> org.apache.lucene.index.IndexWriter.commitInternal(IndexWriter.java:4160)
> > at org.apache.lucene.index.IndexWriter.commit(IndexWriter.java:4122)
> > at
> >
> org.apache.solr.update.DirectUpdateHandler2.commit(DirectUpdateHandler2.java:872)
> > at
> >
> org.apache.solr.update.processor.RunUpdateProcessorFactory$RunUpdateProcessor.processCommit(RunUpdateProcessorFactory.java:100)
> > at
> >
> org.apache.solr.update.processor.UpdateRequestProcessor.processCommit(UpdateRequestProcessor.java:66)
> > at
> >
> org.apache.solr.update.processor.DistributedUpdateProcessor.doLocalCommit(DistributedUpdateProcessor
> >
> > - Rahul
> >
> > On Sat, Oct 10, 2026 at 5:57 PM Jan Høydahl <[email protected]> wrote:
> >
> > > The changelog lists "Dependency Upgrades (61 changes)"
> > > I thought we were to hand edit and de-duplicate that list.
> > >
> > > PS: Jetty 12.1.14 hits branch_10x soon, hope it can make it if there's
> a
> > > respin.
> > >
> > > Jan
> > >
> > > > 10. okt. 2026 kl. 15:48 skrev Andrzej Białecki <[email protected]>:
> > > >
> > > > Please vote for release candidate 2 for Solr 10.1.0
> > > >
> > > > The artifacts can be downloaded from:
> > > >
> > >
> https://dist.apache.org/repos/dist/dev/solr/solr-10.1.0-RC2-rev-dfda5e1d4821958e60d13aa5ce3a0d4992319ed1
> > > >
> > > > You can run the smoke tester directly with this command:
> > > >
> > > > python3 -u dev-tools/scripts/smokeTestRelease.py \
> > > >
> > >
> https://dist.apache.org/repos/dist/dev/solr/solr-10.1.0-RC2-rev-dfda5e1d4821958e60d13aa5ce3a0d4992319ed1
> > > >
> > > > You can build a release-candidate of the official docker images
> (full &
> > > slim) using the following command:
> > > >
> > > > SOLR_DOWNLOAD_SERVER=
> > >
> https://dist.apache.org/repos/dist/dev/solr/solr-10.1.0-RC2-rev-dfda5e1d4821958e60d13aa5ce3a0d4992319ed1/solr
> > > && \
> > > >  docker build
> > > $SOLR_DOWNLOAD_SERVER/10.1.0/docker/Dockerfile.official-full \
> > > >    --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > >    -t solr-rc:10.1.0-2 && \
> > > >  docker build
> > > $SOLR_DOWNLOAD_SERVER/10.1.0/docker/Dockerfile.official-slim \
> > > >    --build-arg SOLR_DOWNLOAD_SERVER=$SOLR_DOWNLOAD_SERVER \
> > > >    -t solr-rc:10.1.0-2-slim
> > > >
> > > > The vote will be open for 72 hours (not including the Sunday and
> > > Columbus Day), i.e. until 2026-10-15 15:00 UTC.
> > > >
> > > > [ ] +1  approve
> > > > [ ] +0  no opinion
> > > > [ ] -1  disapprove (and reason why)
> > > >
> > > > Here is my +1
> > > > ----
> > > >
> > > > Cheers,
> > > > Andrzej
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: [email protected]
> > > > For additional commands, e-mail: [email protected]
> > > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [email protected]
> > > For additional commands, e-mail: [email protected]
> > >
> > >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

Reply via email to