You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@lucene.apache.org by "Mark Miller (JIRA)" <ji...@apache.org> on 2013/03/11 21:57:13 UTC

[jira] [Resolved] (SOLR-4521) Consider not using 'force' replications in SolrCloud recovery.

     [ https://issues.apache.org/jira/browse/SOLR-4521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mark Miller resolved SOLR-4521.
-------------------------------

    Resolution: Fixed
    
> Consider not using 'force' replications in SolrCloud recovery.
> --------------------------------------------------------------
>
>                 Key: SOLR-4521
>                 URL: https://issues.apache.org/jira/browse/SOLR-4521
>             Project: Solr
>          Issue Type: Improvement
>          Components: SolrCloud
>            Reporter: Mark Miller
>            Assignee: Mark Miller
>             Fix For: 4.2, 5.0
>
>
> Now that replication has some better tests and bugs fixed, we may be able to stop forcing a replication on every replication call and let the snap pull determine if one is actually needed. This never worked quite right in the past, so I got around it by forcing a replication on recovery whether it was needed or not - the peer sync phase made this not the biggest deal. However, there are cases where it would still be useful - see SOLR-4519.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org