You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Ludovic Boutros (JIRA)" <ji...@apache.org> on 2015/09/24 19:38:04 UTC
[jira] [Comment Edited] (SOLR-8030) Transaction log does not store
the update chain used for updates
[ https://issues.apache.org/jira/browse/SOLR-8030?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906706#comment-14906706 ]
Ludovic Boutros edited comment on SOLR-8030 at 9/24/15 5:38 PM:
----------------------------------------------------------------
Update of the test.
I have a problem with this test, it creates inconsistent replicas (On my mac).
This prevents the real update chain testing.
was (Author: lboutros):
Update of the test.
I have a problem with this test, it creates incoherent replicas (On my mac).
This prevents the real update chain testing.
> 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-test.patch, SOLR-8030-test.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-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org