Chris,
thanks for taking a look.
On 06 Oct 2014, at 04:44, Chris Lohfink wrote:
> It appears you are aware of the tombstones affect that leads people to label
> this an anti-pattern. Without "due" or any time based value being part of
> the partition key means you will still get a lot of bui
It appears you are aware of the tombstones affect that leads people to label
this an anti-pattern. Without "due" or any time based value being part of the
partition key means you will still get a lot of buildup. You only have 1
partition per shard which just linearly decreases the tombstones.
Hi,
I have put together some thoughts on realizing simple queues with Cassandra.
https://github.com/algermissen/cassandra-ruby-queue
The design is inspired by (the much more sophisticated) Netfilx approach[1] but
very reduced.
Given that I am still a C* newbie, I’d be very glad to hear some th
Shabab,If you are hitting this limit because you are inserting a lot of (CQL)
rows in a single batch I suggest you split the statement up in multiple smaller
batches. Generally, large inserts like this will not perform very well.
Cheers,
Jens
—
Sent from Mailbox
On Fri, Oct 3, 2014 at 6:4
Hi,
I know that this question might look silly, but I really need to know how
the cassandra stress tool works.
I developed my data model and used Cassandra-Stress tool with "u" option
where you pass your own data-model for column family (Table in CQL )and
distribution of each column in the column
Thanks Shane.
best,
/Shahab
On Fri, Oct 3, 2014 at 6:51 PM, Shane Hansen wrote:
> It appears to be configurable in cassandra.yaml
> using batch_size_warn_threshold
>
> https://issues.apache.org/jira/browse/CASSANDRA-6487
>
>
> On Fri, Oct 3, 2014 at 10:47 AM, shahab wrote:
>
>> Hi,
>>
>> I am
