Re: Using CCM with Opscenter and manual agent installation

Thanks Michael for the reply. I'm quite new to Cassandra, so it make sense to explain the use case. I just want to try different choices of data modelling and compare number of reads and writes. At the moment I'm not interested in a real stress test, I just want to understand implications of my

External authentication options for C* (no DSE)

Hi, while for DSE versions of C* it's quite clear what external authentication options are available, I'm not sure about DSC or Apache versions. Can anyone point me to the right documentation on or provide a list of possibilities? Thank you in advance. giampaolo

Re: External authentication options for C* (no DSE)

Search a bit deeper in DSE docs, I've found this: http://www.datastax.com/wp-content/themes/datastax-2014-08/files/FF-DataStax-AdvancedSecurity.pdf . Pratically no external authentication is available for Apache Cassandra. giampaolo 2015-12-23 15:13 GMT+01:00 Giampaolo Trapasso

Re: how to force cassandra-stress to actually generate enough data

I do not know if it can really help in your situation, but from NGCC notes I discovered the existence of GatlingCQL ( https://github.com/gatling-cql/GatlingCql) as an alternative to cassandra-stress. In particular you can tweak a bit the data generation part. giampaolo 2016-06-16 10:33

Re: Using CCM with Opscenter and manual agent installation

> I believe the issue is just jmx_host needing to be set to 'localhost' Yes, that solved. Thanks! giampaolo 2016-01-08 5:17 GMT+01:00 Nick Bailey : > stomp_interface is the address to connect back to the central OpsCenter > daemon with, so 127.0.0.1 should be correct. I

Re: Writing a large blob returns WriteTimeoutException

"If not exists" was an oversight of a previous test. Removing it solved the problem. Thanks a lot, Jim! giampaolo 2016-02-09 1:21 GMT+01:00 Jim Ancona : > The "if not exists" in your INSERT means that you are incurring a > performance hit by using Paxos. Do you need that?

Writing a large blob returns WriteTimeoutException

Hi to all, I'm trying to put a large binary file (> 500MB) on a C* cluster as fast as I can but I get some (many) WriteTimeoutExceptions. I created a small POC that isolates the problem I'm facing. Here you will find the code: https://github.com/giampaolotrapasso/cassandratest, *Main details

Re: Writing a large blob returns WriteTimeoutException

ation.conf *)* Giampaolo 2016-02-08 23:25 GMT+01:00 Jack Krupansky <jack.krupan...@gmail.com>: > You appear to be writing the entire bob on each chunk rather than the > slice of the blob. > > -- Jack Krupansky > > On Mon, Feb 8, 2016 at 1:45 PM, Giampaolo Trapasso < >

Re: Writing a large blob returns WriteTimeoutException

> of records? Seems like you should be computing number of chunks from blob > size divided by chunk size. And it still seems like you are writing the > same data for each chunk. > > -- Jack Krupansky > > On Mon, Feb 8, 2016 at 5:34 PM, Giampaolo Trapasso < > giampaolo.trap

Understanding Cassandra tuning

Hi to all, I want to understand better Cassandra 2.2.5 tuning for my app (and C* tuning in general). In the app I'm developing, the typical scenario is the upload on cluster of a large binary file (in the order of GBs). Long story short, after many failed try to get specific upload throughput

Re: Understanding Cassandra tuning

ight trigger some AWS throttling. > > > > -- Jack Krupansky > > On Fri, Mar 25, 2016 at 11:42 AM, Giampaolo Trapasso < > giampaolo.trapa...@radicalbit.io> wrote: > >> Hi to all, >> >> I want to understand better Cassandra 2.2.5 tuning for my app (and C