[
https://issues.apache.org/jira/browse/SOLR-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14790722#comment-14790722
]
ludovic Boutros commented on SOLR-8030:
---------------------------------------
True, this bug is initialy pointing out that the default chain was always used
for the replay.
But it seems to be more complicated like you said.
The DistributedUpdateProcessor seems to buffer updates in the tLog while in
inactive state.
So you're right, only replaying to RunUpdateProcessor would be a mistake.
But the DirectupdateHandler2 seems to add updates in the tLog while in active
state.
And replaying from the beginning of the default update chain seems to be a
mistake 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
>
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
