lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Commented] (SOLR-8030) Transaction log does not store the update chain used for updates
Date Mon, 21 Mar 2016 13:23:25 GMT


David Smiley commented on SOLR-8030:

Thanks for your tireless effors on this [~lboutros]; I'd like to pursue getting your patch
committed, or some variant of it.  There's definitely a bug today in that PeerSync is grabbing
the default URP chain.  I ran into this bug.  Your patch does the right thing here -- DistributedURP
+ RunURP.  What I don't understand is why you feel that the UpdateLog should keep track of
the original URP chain used.  I'd like to have URPs run exactly once for any document (notwithstanding
Distrib & RunUpdate which are special).

> Transaction log does not store the update chain used for updates
> ----------------------------------------------------------------
>                 Key: SOLR-8030
>                 URL:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message