[
https://issues.apache.org/jira/browse/SOLR-6683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Forest Soup updated SOLR-6683:
------------------------------
Description:
If there are >100 docs gap between the recovering node and the good node, the
solr will do snap pull recovery instead of peersync.
Can the 100 docs be configurable? For example, there can be 10000, 1000, or 10
docs gap between the good node and the node to recover.
For 100 doc, a regular restart of a solr node will trigger a full recovery,
which is a huge impact to the performance of the running systems
Thanks!
was:
If there are >100 docs gap between the recovering node and the good node, the
solr will do snap pull recovery instead of peersync.
Can the 100 docs be configurable? For example, there can be 10000, 1000, or 10
docs gap between the good node and the node to recover.
Thanks!
> Need a configurable parameter to control the doc number between peersync and
> the snapshot pull recovery
> -------------------------------------------------------------------------------------------------------
>
> Key: SOLR-6683
> URL: https://issues.apache.org/jira/browse/SOLR-6683
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 4.7
> Environment: Redhat Linux 64bit
> Reporter: Forest Soup
> Priority: Critical
> Labels: performance
>
> If there are >100 docs gap between the recovering node and the good node, the
> solr will do snap pull recovery instead of peersync.
> Can the 100 docs be configurable? For example, there can be 10000, 1000, or
> 10 docs gap between the good node and the node to recover.
> For 100 doc, a regular restart of a solr node will trigger a full recovery,
> which is a huge impact to the performance of the running systems
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
