epugh commented on code in PR #4010:
URL: https://github.com/apache/solr/pull/4010#discussion_r2662374872
##########
solr/core/src/test/org/apache/solr/cloud/TestCloudConsistency.java:
##########
@@ -59,6 +59,7 @@ public void setupCluster() throws Exception {
System.setProperty("solr.directoryFactory",
"solr.StandardDirectoryFactory");
System.setProperty("solr.ulog.numRecordsToKeep", "1000");
System.setProperty("leaderVoteWait", "60000");
+ System.setProperty("tests.zk.violationReportAction", "IGNORE");
Review Comment:
Wasn't sure where to document this, but I asked Claude for help on why the
test failed sometimes, but not when I run just the single test with the seed.
The response was:
The issue you encountered was due to ZooKeeper watch limits in the test
framework. The `TestCloudConsistency` test creates a complex cloud setup with 4
nodes, network proxies, and performs various cluster operations that create
many ZooKeeper watches. The test framework's default watch limit was set very
low (1), causing the test to fail with "Maximum concurrent create/delete
watches above limit" errors.
- TestCloudConsistency` was missing the system property
`tests.zk.violationReportAction=IGNORE` that other similar complex cloud tests
use
- The test creates many ZooKeeper watches during cluster operations
(collection creation, replica management, network partitioning, etc.)
- The default watch limits in the test framework were too restrictive for
this test
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
