[SOLR-4521] Consider not using 'force' replications in SolrCloud recovery.

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 4.2, 6.0
• Component/s: SolrCloud
• Assignee: Mark Miller
• Reporter: Mark Miller
• Created: 01/Mar/13 14:00
• Updated: 09/May/16 18:54
• Resolved: 11/Mar/13 20:56

Description

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.

Issue Links

• depends upon: SOLR-4511 Repeater doesn't return correct index version to slaves
• relates to: SOLR-4519 corrupt tlog causes fullCopy download index files every time reboot a node