[ 
https://issues.apache.org/jira/browse/SOLR-11660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461845#comment-16461845
 ] 

Shawn Heisey commented on SOLR-11660:
-------------------------------------

Trying to reproduce this with version 7.3.0 on the cloud example.  I created a 
'techproducts' collection with 4 shards, 2 replicas, indexed the example docs 
to it, then followed the reproduction steps.  I got this error trying to 
restore, which is a separate issue:

"org.apache.solr.common.SolrException:org.apache.solr.common.SolrException: 
Solr cloud with available number of nodes:2 is insufficient for restoring a 
collection with 4 shards, total replicas per shard 1 and maxShardsPerNode -1. 
Consider increasing maxShardsPerNode value OR number of available nodes."

Then I added parameters to the restore command, including replicationFactor=2, 
but when it got restored, there was only one replica.  So I'm not sure what I 
need to do in order to get two replicas.

> 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
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to