lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (SOLR-11069) CDCR bootstrapping can get into an infinite loop when a core is reloaded
Date Wed, 16 Aug 2017 23:10:00 GMT

    [ https://issues.apache.org/jira/browse/SOLR-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129591#comment-16129591
] 

ASF subversion and git services commented on SOLR-11069:
--------------------------------------------------------

Commit a850749ab32e57d0bd96a8517798febeaad9dec1 in lucene-solr's branch refs/heads/branch_7x
from [~erickerickson]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=a850749 ]

SOLR-11069: CDCR bootstrapping can get into an infinite loop when a core is reloaded

(cherry picked from commit ac97931)


> CDCR bootstrapping can get into an infinite loop when a core is reloaded
> ------------------------------------------------------------------------
>
>                 Key: SOLR-11069
>                 URL: https://issues.apache.org/jira/browse/SOLR-11069
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: CDCR
>    Affects Versions: 6.2, 6.3, 6.4, 6.5, 6.6, 7.0
>            Reporter: Amrit Sarkar
>            Assignee: Erick Erickson
>         Attachments: SOLR-11069.patch, SOLR-11069.patch, SOLR-11069.patch
>
>
> {{LASTPROCESSEDVERSION}} (a.b.v. LPV) action for CDCR breaks down due to poorly initialised
and maintained buffer log for either source or target cluster core nodes.
> If buffer is enabled for cores of either source or target cluster, it return {{-1}},
*irrespective of number of entries in tlog read by the {{leader}}* node of each shard of respective
collection of respective cluster. Once disabled, it starts telling us the correct LPV for
each core.
> Due to the same flawed behavior, Update Log Synchroniser may doesn't work properly as
expected, i.e. provides incorrect seek to the {{non-leader}} nodes to advance at. I am not
sure whether this is an intended behavior for sync but it surely doesn't feel right.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message