Maybe Tim you may have an opinion on this one as you introduced this watch limit violation checker in https://issues.apache.org/jira/browse/SOLR-6370 ? Running just about any SolrCloud based test will cause this to dump some info at the end. Even simple ones like org.apache.solr.client.solrj.impl.CloudSolrClientTest#queryWithLocalShardsPreferenceRulesTest
10089 WARN (ZkTestServer Run Thread) [] o.a.s.c.ZkTestServer Watch limit violations: Maximum concurrent create/delete watches above limit: 13 /solr/collections/localShardsTestColl/terms/shard2 13 /solr/collections/localShardsTestColl/terms/shard1 9 /solr/collections/localShardsTestColl/terms/shard3 4 /solr/aliases.json 4 /solr/clusterprops.json 3 /solr/collections/localShardsTestColl/collectionprops.json 3 /solr/packages.json 3 /solr/security.json 3 /solr/configs/conf Maximum concurrent data watches above limit: 51 /solr/collections/localShardsTestColl/state.json Maximum concurrent children watches above limit: 23 /solr/collections/localShardsTestColl/state.json 16 /solr/live_nodes 8 /solr/collections 3 /solr/overseer/collection-queue-work ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Wed, Feb 17, 2021 at 5:20 PM David Smiley <[email protected]> wrote: > I've noticed that it's quite common for a SolrCloud based test to conclude > with warnings about "Watch limit violations". I don't know how to > interpret these violations; it's normal to get them. Can someone offer > insights as to what this matter is about and what we ought to do about it? > > 63605 WARN (ZkTestServer Run Thread) [ ] o.a.s.c.ZkTestServer Watch > limit violations: > Maximum concurrent create/delete watches above limit: > > 4 /solr/aliases.json > 4 /solr/clusterprops.json > 3 /solr/packages.json > 3 /solr/security.json > 2 /solr/collections/ping_test/terms/shard2 > 2 /solr/collections/ping_test/terms/shard1 > 2 /solr/configs/conf > > ~ David Smiley > Apache Lucene/Solr Search Developer > http://www.linkedin.com/in/davidwsmiley >
