[
https://issues.apache.org/jira/browse/SOLR-8797?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker closed SOLR-8797.
-------------------------------
Resolution: Not A Problem
Assignee: Varun Thacker
Hi Gerald,
Yes this will happen now. Currently Solr supports backup and restore of cores .
When SOLR-5750 is complete this problem will be solved since Solr will support
backup/restore of a cloud collection. There backups will only be taken against
the leaders.
Currently as a workaround you can use the CLUSTERSTATUS Collection API to fetch
the leaders of replicas and issue a backup against those specific nodes
> Backup command on a recovering index should fail
> ------------------------------------------------
>
> Key: SOLR-8797
> URL: https://issues.apache.org/jira/browse/SOLR-8797
> Project: Solr
> Issue Type: Bug
> Affects Versions: 5.0
> Environment: Several Solr servers on a cloud mode
> Reporter: Gérald Reinhart
> Assignee: Varun Thacker
> Priority: Minor
>
> We are using the backup command "http:// ...
> /replication?command=backup&location=/tmp" against one server of the
> cluster.
> Most of the time there is no issue with this command.
> But in some particular case, the server can be in recovery mode. In
> this case, the command is doing a backup on an index that is not
> complete and return a http code 200. We end up with a partial index
> backup ! As a workaround we will do this backup against the leader of
> the cloud: the leader is never in recovery mode.
> In our opinion, the backup command on a recovering index should
> return a http code 503 Service Unavailable (and not http code 200 OK).
> [Mail in the mail
> list|http://mail-archives.apache.org/mod_mbox/lucene-solr-user/201603.mbox/%3C56D56004.70905%40kelkoo.com%3E]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
