[
https://issues.apache.org/jira/browse/SOLR-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221309#comment-15221309
]
Ludovic Boutros commented on SOLR-8030:
---------------------------------------
[~dsmiley], if I remember the process correctly[~dsmiley], if I remember the
process correctly (I checked this a long time ago now ;)), there are two
different cases :
- the first one is is the "normal" case, the URP chain is used and the
DirectUpdateHandler adds the documents to the UpdateLog.
- the second one is used during recovery when updates must be buffered and the
URP chain is not used before buffering documents to the UpdateLog. And the
buffering is done by the DistributedURP.
That's why you will find two different places where documents are added to the
UpdateLog and that's why two different URP chain should be put in the UpdateLog
(see my old comment on that subject).
> 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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
