You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Robert Elwell (JIRA)" <ji...@apache.org> on 2016/11/22 05:52:58 UTC
[jira] [Created] (SOLR-9791) Collections API Async Backup / Restore
Status Misleading
Robert Elwell created SOLR-9791:
-----------------------------------
Summary: Collections API Async Backup / Restore Status Misleading
Key: SOLR-9791
URL: https://issues.apache.org/jira/browse/SOLR-9791
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Affects Versions: 6.2.1
Reporter: Robert Elwell
I seem to be running into a problem where restoring a backup to a given collection using the async feature reports that the backup has completed, but the collection is empty. All shards, and there are no errors in the logs. However, I still see in the logs:
{code}
org.apache.solr.handler.RestoreCore; Copying file _xxx.xx to restore directory
{code}
It sounds to me like this would mean that restoration is _not_ in fact complete.
Would it be possible to have the async functionality more accurately report the restoration of a backup? Alternately, am I missing an API functionality I should be referring to?
Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org