[
https://issues.apache.org/jira/browse/SOLR-11069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16129614#comment-16129614
]
ASF subversion and git services commented on SOLR-11069:
--------------------------------------------------------
Commit 34139f7deb698611046263503272267179c0d315 in lucene-solr's branch
refs/heads/branch_7_0 from [~erickerickson]
[ https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;h=34139f7 ]
SOLR-11069: CDCR bootstrapping can get into an infinite loop when a core is
reloaded
(cherry picked from commit ac97931c7e5800b2e314545f54c4d524eb69b73b)
> 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: [email protected]
For additional commands, e-mail: [email protected]
