[
https://issues.apache.org/jira/browse/SOLR-11660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Varun Thacker resolved SOLR-11660.
----------------------------------
Resolution: Duplicate
> Issue while update index in collection after collection restore on Solr Cloud
> -----------------------------------------------------------------------------
>
> Key: SOLR-11660
> URL: https://issues.apache.org/jira/browse/SOLR-11660
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Backup/Restore, SolrCloud
> Affects Versions: 6.4.1
> Environment: CentOs7.3 Solr 6.4.1 Zookeeper 3.4.6
> Reporter: Viachaslau Kabak
> Assignee: Varun Thacker
> Priority: Critical
> Fix For: 7.4, master (8.0)
>
>
> We use to backup and restore one of our collections in solrCloud.
> if not to restore collection but to create it and fill from application - the
> second attempt to renew application index is successful both on leader and
> followers. But is to restore collection and then to renew index from
> application - we have new index on follower and old index on leader.
> The Reload on collection helps to make index up-to-date on leader.
> In logs we have {{o.a.s.u.p.DistributedUpdateProcessor Ignoring commit while
> not ACTIVE - state: BUFFERING replay: false}}
> If to restart solr service before collection update from application - index
> on all solr servers is updated.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
