lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Erick Erickson (JIRA)" <>
Subject [jira] [Updated] (SOLR-11069) LASTPROCESSEDVERSION for CDCR is flawed when buffering is enabled
Date Tue, 15 Aug 2017 01:05:00 GMT


Erick Erickson updated SOLR-11069:
    Attachment: SOLR-11069.patch

This one against master. 

Fixes precommit and has documentation changes.

All tests pass.

I need to go over the doc changes again, but this is what it's looking like at this point.
The major changes are an admonition about buffering and some explanation about what it's for.

> LASTPROCESSEDVERSION for CDCR is flawed when buffering is enabled
> -----------------------------------------------------------------
>                 Key: SOLR-11069
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: CDCR
>    Affects Versions: 7.0
>            Reporter: Amrit Sarkar
>            Assignee: Erick Erickson
>         Attachments: 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

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

View raw message