[
https://issues.apache.org/jira/browse/SOLR-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14747282#comment-14747282
]
ludovic Boutros commented on SOLR-8030:
---------------------------------------
I think [[email protected]] is right.
It seems that log entries are added at the end of the update processor chain
and replayed from the beginning of the default processor chain.
The replayed commands are local commands, so I think that pre-distributed
processors are bypassed, but the other processors seem to be used.
Why the log replay does not use the _RunUpdateProcessor_ directly, instead of
the full update chain ?
> 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
>
> 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]
