[
https://issues.apache.org/jira/browse/SOLR-11448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16289844#comment-16289844
]
ASF subversion and git services commented on SOLR-11448:
--------------------------------------------------------
Commit 44cc0defe8f9ba884c50d1c6d2c1cd5a3eb7bf32 in lucene-solr's branch
refs/heads/master from [~ctargett]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=44cc0de ]
SOLR-11753: copy edits; add docs for SOLR-11448
> 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
