[
https://issues.apache.org/jira/browse/SOLR-11448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300258#comment-16300258
]
David Smiley commented on SOLR-11448:
-------------------------------------
[~ab] Would this feature make SOLR-8416 obsolete? At least I am looking
expressly at CollectionsHandler.invokeAction calling waitForActiveCollection on
line 252. Instead we could pass CommonAdminParams.WAIT_FOR_FINAL_STATE as a
param, or in fact make this default to true? Although there is a
distinction... waitForActiveCollection uses a checkLeaderOnly setting and thus
could return sooner/faster. The last sentence in this issue makes the
distinction between "completed" vs "active" so I suppose
waitForActiveCollection is still needed. I guess I hoped for
CommonAdminParams.WAIT_FOR_FINAL_STATE to be something more than it may be...
why wouldn't we always want to wait for final state (assuming this isn't an
async call)?
> Implement an option in collection commands to wait for command results
> ----------------------------------------------------------------------
>
> Key: SOLR-11448
> URL: https://issues.apache.org/jira/browse/SOLR-11448
> Project: Solr
> Issue Type: Sub-task
> Security Level: Public(Default Security Level. Issues are Public)
> Components: AutoScaling
> Affects Versions: 7.2
> Reporter: Andrzej Bialecki
> Assignee: Andrzej Bialecki
> Fix For: 7.2, master (8.0)
>
> Attachments: SOLR-11448.diff
>
>
> In order to reliably track results and impact of executing collection-level
> commands in the autoscaling framework we need an option to execute the
> requested operation (eg. move replica) and then wait for the operation
> results to actually take effect (the replica has been moved AND it became
> active).
> This is different than executing commands synchronously, in which case the
> API only waits for the operation itself to be completed (eg. moving the
> replica succeeded) but it does not wait for the final effects of this
> operation to take place (eg. the replica becomes active).
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
