[
https://issues.apache.org/jira/browse/SOLR-11652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16259966#comment-16259966
]
Amrit Sarkar commented on SOLR-11652:
-------------------------------------
More details on the behavior:
1. Cdcr target leader's tlogs doesn't get purged unless issues action=START at
target
2. Cdcr source leader's tlogs doesn't get purged when DISABLEBUFFER from API.
3. Cdcr source if restarted, with DISABLEBUFFER from API earlier, behaves
normally.
4. The #3 point is expected, as source will read buffer config from ZK and load
and mark tlogs at beginning, similarly reading from solrconfig.xml
> Cdcr TLogs doesn't get purged for Source collection Leader when Buffer is
> disabled from CDCR API
> ------------------------------------------------------------------------------------------------
>
> Key: SOLR-11652
> URL: https://issues.apache.org/jira/browse/SOLR-11652
> Project: Solr
> Issue Type: Bug
> Security Level: Public(Default Security Level. Issues are Public)
> Reporter: Amrit Sarkar
>
> Cdcr transactions logs doesn't get purged on leader EVER when Buffer DISABLED
> from CDCR API.
> Steps to reproduce:
> 1. Setup source and target collection cluster and START CDCR, BUFFER ENABLED.
> 2. Index bunch of documents into source; make sure we have generated tlogs in
> decent numbers (>20)
> 3. Disable BUFFER via API on source and keep on indexing
> 4. Tlogs starts to get purges on follower nodes of Source, but Leader keeps
> on accumulating ever.
--
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
