[ 
https://issues.apache.org/jira/browse/CASSANALYTICS-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jyothsna Konisa updated CASSANALYTICS-124:
------------------------------------------
                        Authors: Jyothsna Konisa
    Test and Documentation Plan: Added unit testing and verified fix with CCM 
and stress test.
                         Status: Patch Available  (was: Open)

> Commitlog reading not progressing in CDC due to incorrect 
> CommitLogReader.isFullyRead 
> --------------------------------------------------------------------------------------
>
>                 Key: CASSANALYTICS-124
>                 URL: https://issues.apache.org/jira/browse/CASSANALYTICS-124
>             Project: Apache Cassandra Analytics
>          Issue Type: Improvement
>          Components: CDC
>            Reporter: Jyothsna Konisa
>            Assignee: Jyothsna Konisa
>            Priority: Normal
>             Fix For: 0.4
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> In the CDC code path after all the commit logs are listed, CdcScannerBuilder 
> opens commit logs one by one and the commit log reading is not progressing 
> after reading the first one for the following reasons.
> CommitLogReader.isFullyRead() incorrectly returns false even when the commit 
> log is fully in following scenarios.
> 1. After the restart when the CDC state is loaded, 
> BufferingCommitLogReader.position is not updated to the marker.start position 
> and remains 0 affecting the result of above method
> 2. While reading commit log segments with padded zeros, even after the commit 
> log is read, the above method returns false. 
> For both the issues the fix is setting the BufferingCommitLogReader.position 
> correctly after loading the state and after finishing reading the segment.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to