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

ASF subversion and git services commented on SOLR-17453:
--------------------------------------------------------

Commit 72ad7b88013bc211e08abd91b1999d1b49b0bfa0 in solr's branch 
refs/heads/branch_9x from Pierre Salagnac
[ https://gitbox.apache.org/repos/asf?p=solr.git;h=72ad7b88013 ]

SOLR-17453: Drop CloudUtil.waitForState() in favor of common waitForState() 
(#2716)

Update tests so they use the standard ZkStateReader.waitForState(),
relying on a Zookeeper watch, instead of actively polling the collection
state.

(cherry picked from commit 7d6088381d918e4a94e8c3d2c20c1eb5be003186)


> Replace CloudUtil.waitForState and some TimeOut with 
> ZkStateReader.waitForState
> -------------------------------------------------------------------------------
>
>                 Key: SOLR-17453
>                 URL: https://issues.apache.org/jira/browse/SOLR-17453
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>            Reporter: David Smiley
>            Priority: Minor
>              Labels: newdev, pull-request-available
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> We should universally use ZkStateReader.waitForState when waiting for the 
> ClusterState to change based on a predicate.  SolrCloudTestCase.waitForState 
> is fine since it calls the former.  But CloudUtil.waitForState does not; it 
> should be replaced.  Additionally, TimeOut is used in some places wait 
> waitForState ought to be used, like CreateCollectionCmd.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@solr.apache.org
For additional commands, e-mail: issues-h...@solr.apache.org

Reply via email to