[
https://issues.apache.org/jira/browse/SOLR-11720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16277023#comment-16277023
]
Erick Erickson commented on SOLR-11720:
---------------------------------------
Please raise questions like this on the user's list first, that way we can
gather information about what you're seeing. In this case I have several
quesitons:
1> did you issue a commit after the restore was complete?
2> Do you have excessive autowarming set up? If your autowarming takes a long
time, then the restore is fine. The old searcher was serving requests until
autowarming finished.
3> how long is "eventually"? Seconds? Minutes? Hours? Details matter.
4> are you absolutely sure you weren't getting hits from a non-Solr cache
(browser, something between and Solr etc.)?
Best,
Erick
> Backup restore command completes before index is ready
> ------------------------------------------------------
>
> Key: SOLR-11720
> URL: https://issues.apache.org/jira/browse/SOLR-11720
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: SolrCloud
> Affects Versions: 7.1
> Reporter: Vitaly Lavrov
>
> Scenario:
> 1. Run backup restore as async command
> 2. Check command status until it has 'completed' status
> 3. Query collection immediately for total number of documents
> The problem is the query will return incorrect number. The query will return
> correct number eventually if one keeps querying.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
