Amrit Sarkar created SOLR-11069: ----------------------------------- Summary: LASTPROCESSEDVERSION for CDCR (both source and target) is flawed when buffering is enabled 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: 7.0 Reporter: Amrit Sarkar
{{LASTPROCESSEDVERSION}} (a.b.v. LPV) action for CDCR breaks down terribly due to poorly initialised and maintained buffer log for source 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 correct 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-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org