> Semi-lame post to this mailing list i guess :( I should have checked that
> earlier
No problems.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
New Zealand
@aaronmorton
http://www.thelastpickle.com
On 17/01/2013, at 11:50 PM, Reik Schatz wrote:
> Cool feature, didn't
Cool feature, didn't know it existed. It turned however out that everything
works fine! There was a configuration error that duplicated a AWS sns->sqs
subscription, so we go twice the amount of data delivered to our
application. Semi-lame post to this mailing list i guess :( I should have
checked t
You *may* be seeing this https://issues.apache.org/jira/browse/CASSANDRA-2503
It was implemented in 1.1.0 but perhaps data in the original cluster is more
compacted than the new one.
Are the increases for all CF's are just a few?
Do you have a work load of infrequent writes to rows followed by
