Make startJettySolrRunner implicitly wait for node to join cluster#33
Draft
Make startJettySolrRunner implicitly wait for node to join cluster#33
startJettySolrRunner implicitly wait for node to join cluster#33Conversation
Co-authored-by: epugh <22395+epugh@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Analyze waitForNode usage after startJettySolrRunner
Make Mar 19, 2026
startJettySolrRunner implicitly wait for node to join cluster
dsmiley
approved these changes
Mar 19, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
MiniSolrCloudCluster.startJettySolrRunner()returned immediately after starting the Jetty process, without waiting for the node to appear in ZooKeeper live nodes. Tests had to explicitly callcluster.waitForNode(jetty, 30)afterward — and many didn't, creating silent race conditions.Core fix
Added
waitForNode(jetty, DEFAULT_TIMEOUT)to both corestartJettySolrRunnerimplementations so all overloads inherit the guarantee:startJettySolrRunner(String name, JettyConfig config, String solrXml)— guarded bysolrClient != nullsince the constructor invokes this in parallel before the client is built (the constructor's existingwaitForAllNodeshandles that phase)startJettySolrRunner(JettySolrRunner jetty, boolean reusePort)— unconditional; only called post-constructionCleanup
Removed now-redundant explicit wait calls from 8 test files:
waitForNode(...)afterstartJettySolrRunnerinFullSolrCloudDistribCmdsTest,ClusterEventProducerTestwaitForAllNodes(...)immediately after a singlestartJettySolrRunnerinTestMiniSolrCloudClusterSSL,TestCollectionsAPIViaSolrCloudCluster,TestCloudSearcherWarming,TestCloudSolrClientConnections,TestCollectionStateWatcherswaitForAllNodescalls that follow batched/parallel restarts or serve as broader sanity checks are intentionally left in place.Warning
Firewall rules blocked me from connecting to one or more addresses (expand for details)
I tried to connect to the following addresses, but was blocked by firewall rules:
develocity.apache.org/usr/lib/jvm/temurin-21-jdk-amd64/bin/java /usr/lib/jvm/temurin-21-jdk-amd64/bin/java -XX:ReservedCodeCacheSize=256m -XX:TieredStopAtLevel=1 -XX:+UseParallelGC -XX:ActiveProcessorCount=1 --add-exports jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.file=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.parser=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.tree=ALL-UNNAMED --add-exports jdk.compiler/com.sun.tools.javac.util=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED --add-opens=java.base/java.lang=ALL-UNNAMED --add-opens=java.base/java.lang.invoke=ALL-UNNAMED --add-opens=java.prefs/java.util.prefs=ALL-UNNAMED --add-exports=jdk.compiler/com.sun.tools.javac.api=ALL-UNNAMED(dns block)If you need me to access, download, or install something from one of these locations, you can either:
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.