+1 (non-binding)
SUCCESS! [2:03:32.338793] Smoke tester on macOS (x86_64), JDK 21. Tried basic indexing and queries in standalone and SolrCloud on Windows. Upgraded a Solr 8.x index on Solr 9.11 with the UPGRADEINDEX CoreAdmin API , and opened it on Solr 10.1 with this RC (since the Lucene change that makes this possible is part of Lucene 10.4 ( https://github.com/apache/lucene/pull/14607)). Index opens fine! Ran into one consistent failure with a CPUCircuitBreaker test on JDK 23 (which I was running by default initially). Claude analysis (snippet below) says it is because the call to getCpuLoad() returns NaN when called subsequently at very short intervals. Works fine on JDK 21. Pressed Claude further and this looks like a JDK 23 and 24 specific issue. Not reproducible on JDK 21 and 25 LTS releases. And so I am inclined to still +1 this. Did not dig in into the mitigation, but hunch is this is something that might be ok to handle in the test (probably by tweaking sleep interval?). 1. TestCircuitBreakers.testCPUCircuitBreakerReadsLiveUsage (2 runs) and PlacementPluginIntegrationTest.testAttributeFetcherImpl (2 runs) Both read the OTel gauge jvm_system_cpu_utilization. OTel records nothing when OperatingSystemMXBean.getCpuLoad() returns NaN, and on JDK 23.0.2/macOS it very often does (1999/2000 back-to-back calls, 66/100 calls 50ms apart). JDK 21.0.10 and 25 returned 0 NaN in the same probe. Rerunning at the RC commit with the same seed: testAttributeFetcherImpl failed 2/5 iterations on JDK 23, 0/5 on JDK 21. - Rahul On Mon, Oct 26, 2026 at 10:56 AM Jan Høydahl <[email protected]> wrote: > Joel, I tried to reproduce what you see, but all is good here. > Can you try again, perhaps on another machine or other browser? > > Jan > > > 26. okt. 2026 kl. 14:22 skrev Joel Bernstein <[email protected]>: > > > > The smoke tester ran without error for me. But when I went to test out > the > > assets I did the following: > > > > 1) Unpack the tar gz. > > 2) Enter the 10.1.0 dir > > 3) Run: bin/solr start > > 4) Open browser to localhost:8983/solr > > > > I get an admin screen with an error: > > > > "Your user does not have the necessary role(s) to perform this action." > > > > I did the same procedure for 10.0.0 and I don't get this error message. > > > > Is this the desired behavior for 10.1.0? > > > > Joel Bernstein > > http://joelsolr.blogspot.com/ > > > > > > On Thu, Oct 22, 2026 at 6:16 AM Andrzej Białecki <[email protected]> wrote: > > > >> Please vote for release candidate 3 for Solr 10.1.0 > >> > >> The artifacts can be downloaded from: > >> > >> > https://dist.apache.org/repos/dist/dev/solr/solr-10.1.0-RC3-rev-749712b71940c9f96d824c533f32f5c56dcd3924 > >> > >> 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-RC3-rev-749712b71940c9f96d824c533f32f5c56dcd3924 > >> > >> 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-RC3-rev-749712b71940c9f96d824c533f32f5c56dcd3924/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-3 && \ > >> 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-3-slim > >> > >> The vote will be open for at least 72 hours (not counting the weekend) > >> i.e. until 2026-10-27 11: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] > >
