Hi,
I have a 9 node cassandra cluster, each node has:
RAM: 5.5gb
Disk: 64gb
C* version: 3.3
Java: 1.8.0_51
The cluster stores about 2 million rows and partition keys for all these
rows are unique.
I am stress-reading it from a 12-node client cluster.
Each read-client has 50 threads, so total 600
Does Cassandra itself use triggers internally for something?
That would make a pretty good case for triggers being ready for production
use.
Otherwise, it would tend to be a neglected feature because active
developers would have no good reason to add features to it other than just
make the test su
Hi,
I am not able to find any documentation on the current state of triggers
being production ready.
The post at
http://www.datastax.com/dev/blog/whats-new-in-cassandra-2-0-prototype-triggers-support
says that "The current implementation is experimental, and there is some
work to do before trigge
ted in the
cdc_raw_directory
- c) Launch an agent similar to CASSANDRA-11575. Consume and delete the
cdc files?
Thanks for your help,
SG
On Wed, Feb 15, 2017 at 3:19 PM, Jay Zhuang
wrote:
> I tried this CASSANDRA-11575 for 3.8. Works great.
>
> Thanks,
> Jay
>
>
> On 2/15/17 3:08
Hi,
I have gone through several resources mentioned in
http://cassandra.apache.org/doc/latest/operating/cdc.html
The only thing mentioned about reading the CDC is that it is fairly
straightforward with a link to
https://github.com/apache/cassandra/blob/e31e216234c6b57a531cae607e0355666007deb2/src
