[
https://issues.apache.org/jira/browse/CASSANDRA-17666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17551212#comment-17551212
]
Yifan Cai commented on CASSANDRA-17666:
---------------------------------------
Starting commit
CI Results:
||Branch||Source||Circle CI||
|trunk|[branch|https://github.com/yifan-c/cassandra/tree/commit_remote_branch/CASSANDRA-17666-trunk-C82C970A-1A41-43E9-8A1C-72EFD3B80A5F]|[build|https://app.circleci.com/pipelines/github/yifan-c/cassandra?branch=commit_remote_branch%2FCASSANDRA-17666-trunk-C82C970A-1A41-43E9-8A1C-72EFD3B80A5F]|
CI is all green.
> Option to disable write path during streaming for CDC enabled tables
> --------------------------------------------------------------------
>
> Key: CASSANDRA-17666
> URL: https://issues.apache.org/jira/browse/CASSANDRA-17666
> Project: Cassandra
> Issue Type: Improvement
> Components: Feature/Change Data Capture
> Reporter: Yifan Cai
> Assignee: Yifan Cai
> Priority: Normal
> Time Spent: 1h 10m
> Remaining Estimate: 0h
>
> For the CDC-enabled tables, a special write path is employed during
> streaming. The mutations streamed are written into commit log first.
> There are scenarios that the commit logs can accumulate, which lead to
> failure of streaming and blocking writes.
> I'd like to propose adding a dynamic toggle to disable the special write path
> for CDC during streaming.
> Please note that the toggle is a trade-off. Because the special write path is
> there in the hope to ensure data consistency. Turning it off allows the
> streaming to pass, but in some extreme scenarios, the downstream CDC
> consumers may have holes in the stream, depending on how they consumes the
> commit logs.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
