How do I set TTL for cassandra-stress inserts, either in the profile yaml
file (better) or in the command line?
Thanks
Tzach
Are you on the azure premium storage?
http://www.datastax.com/2015/04/getting-started-with-azure-premium-storage-and-datastax-enterprise-dse
Secondary indexes are built for convenience not performance.
http://www.datastax.com/resources/data-modeling
What's your compaction strategy? Your nodes
Sebastian,Thank you so much for providing detailed explanation. I still have
some questions and I need to provide some clarifications
1. We do not have code that is creating the tables dynamically. All DDL
operations are done through Datastax DevCenter tool. When you say schema to
settle, do
We faced similar issue where we had 60k sstables due to coldness bug in 2.0.3.
We solved it by following Datastax recommendation for Production at
http://docs.datastax.com/en/cassandra/1.2/cassandra/install/installRecommendSettings.html
:
Step 1 : Add the following line to /etc/sysctl.conf :
Ironically in my experience the fastest ways to get data into C* are considered
“anti-patterns” by most (but I have no problem saturating multiple gigabit
network links if I really feel like inserting fast)
It’s been a while since I tried some of the newer approaches though (my fast
load code
Hi,
I have a use case wherein I receive a daily batch of data; it's about
50M--100M records (a record is a list of integers, keyed by a
UUID). The target is a 12-node cluster.
Using a simple-minded approach (24 batched inserts in parallel, using
the Ruby client), while the cluster is being read
Hi Saladi,
Recently I faced a similar problem, I had a lot of CFs to fix, so I wrote
this: https://github.com/kluyg/cassandra-schema-fix
I think it can be useful to you.
Kind regards,
Mikhail
On Mon, Jul 13, 2015 at 11:51 AM, Saladi Naidu naidusp2...@yahoo.com
wrote:
Sebastian,
Thank you so
Hi Kevin,
Here is what we use, works for us in production:
https://gist.github.com/kluyg/46ae3dee9000a358edf9
To unit test it, you'll need to check that your custom retry policy returns
the RetryDecision you want for the inputs.
To verify that it works in production, you can wrap it in a
