>
> Actually, the design and initiation of our service is based on the fact
> that the CDC feature in Cassandra is used for streaming data changes in
> Cassandra with low latency. If this is not the case, may I understand
> what's the purpose and the intended use case for the CDC feature in
>
I believe you could set your tables to flush to disk at specific intervals
(memtable_flush_period_in_ms), note that you'd have to set this for all
tables (not just the CDC enabled tables) to ensure that commitlog files are
flushed to the cdc_raw directory. Or as Dhanunjaya noted you could just
One way to flush commitlog is nodetool flush
On Cassandra nodes .
On Tue, May 4, 2021 at 3:58 PM Bingqin Zhou wrote:
> Hi Kane,
>
> Thank you for the insights!
>
> Reducing the total space on its own will help, however definitely test
>> this as such a large drop could result in a massive
Hi Kane,
Thank you for the insights!
Reducing the total space on its own will help, however definitely test this
> as such a large drop could result in a massive increase in SSTables and
> thus compaction overhead. You'll in general want to look into any property
> that makes memtables flush
(removing dev)
commitlog_segment_size_in_mb isn't going to help, in fact you probably
don't want to modify this as it'll reduce the maximum size of your
mutations.
Reducing the total space on its own will help, however definitely test this
as such a large drop could result in a massive increase
Hi,
We're working with the CDC feature to develop an agent to stream changes in
Cassandra DB into Kafka. However, the CDC feature doesn't work well for us
so far because CommitLog files are rarely flushed into cdc_raw directory,
and the frequency can be as low as a few months.
Is there any
