[
https://issues.apache.org/jira/browse/SOLR-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ludovic Boutros updated SOLR-8030:
----------------------------------
Attachment: SOLR-8030.patch
The update chain to use in case of log replay or peersync should be:
DistributedUpdateProcessor => RunUpdateProcessor
The DistributedUpdateProcessor is needed in case of version update.
The update chain should be kept in order to be able to call the finish() method
at the end of log replay or peer sync.
This patch contains updated tests: TestRecovery and PeerSyncTest which check
the (bad) usage of default route. It cannot be called anymore.
It contains a fix as well.
> Transaction log does not store the update chain used for updates
> ----------------------------------------------------------------
>
> Key: SOLR-8030
> URL: https://issues.apache.org/jira/browse/SOLR-8030
> Project: Solr
> Issue Type: Bug
> Components: SolrCloud
> Affects Versions: 5.3
> Reporter: Ludovic Boutros
> Attachments: SOLR-8030.patch
>
>
> Transaction Log does not store the update chain used during updates.
> Therefore tLog uses the default update chain during log replay.
> If we implement custom update logic with multiple update chains, the log
> replay could break this logic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
