You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Mikhail Khludnev (JIRA)" <ji...@apache.org> on 2018/06/25 14:35:00 UTC
[jira] [Commented] (SOLR-9598) Solr RESTORE api doesn't wait for
the restored collection to be fully ready for usage
[ https://issues.apache.org/jira/browse/SOLR-9598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16522350#comment-16522350 ]
Mikhail Khludnev commented on SOLR-9598:
----------------------------------------
is it related to SOLR-12291 ?
> Solr RESTORE api doesn't wait for the restored collection to be fully ready for usage
> -------------------------------------------------------------------------------------
>
> Key: SOLR-9598
> URL: https://issues.apache.org/jira/browse/SOLR-9598
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Affects Versions: 6.2
> Reporter: Hrishikesh Gadre
> Priority: Major
>
> As part of the RESTORE operation, Solr creates a new collection and adds necessary number of replicas to each shard. The problem is that this operation doesn't wait for this new collection to be fully ready for usage (e.g. querying and indexing). This requires extra checks on the client side to make sure that the recovery is complete and reflected in cluster status stored in Zookeeper. e.g. refer to the backup/restore unit test for this check,
> https://github.com/apache/lucene-solr/blob/722e82712435ecf46c9868137d885484152f749b/solr/core/src/test/org/apache/solr/cloud/AbstractCloudBackupRestoreTestCase.java#L234
> Ideally this check should be implemented in the RESTORE operation itself.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org