[ 
https://issues.apache.org/jira/browse/SOLR-17945?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18029118#comment-18029118
 ] 

David Smiley commented on SOLR-17945:
-------------------------------------

[~jdyer] , when you closed the issue, you typed "10x" and "9x" into the fix 
version field.  Please don't do that; it _creates_ Version objects in Jira, 
which we only want to happen by release managers as part of our release 
process.  Instead, pick amongst the existing versions – and in this case: "main 
(10.0)" and "9.10".  I fixed this and deleted the invalid versions.

> Fix flaky test: CloudHttp2SolrClientTest#testHttpCspPerf
> --------------------------------------------------------
>
>                 Key: SOLR-17945
>                 URL: https://issues.apache.org/jira/browse/SOLR-17945
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrJ
>    Affects Versions: main (10.0), 9.9
>            Reporter: James Dyer
>            Assignee: James Dyer
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: main (10.0), 9.10
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Since 9/22/2025 *CloudHttp2SolrClientTest#testHttpCspPerf* has been failing 
> periodically, both in branch_9x and in main/10.x. This test verifies that 
> CloudHttp2SolrClient is properly caching cluster state. See SOLR-14985 for 
> background. The verification counts the logged requests to the CLUSTERSTATUS 
> endpoint and fails if it was called too many times.
> However, with the addition of SOLR-17921, a background process also calls 
> CLUSTERSTATUS.  This can lead to too many calls and periodic test failures.  
> A simple fix is to increase the background task's polling interval to a very 
> large number.  This ensures it never runs while the test is in progress.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to