Re: cassandra.yaml configuration for large machines (scale up vs. scale out)

2017-11-04 Thread Jeff Jirsa
SSDs definitely help. I think JBOD works correctly in newer versions (CASSANDRA-6696 that separates data by token, so you dont have to rebuild the whole node, not sure off the top of my head if there's followup tickets). 10GB probably more useful if you use vnodes than single tokens (likely to

Re: cassandra.yaml configuration for large machines (scale up vs. scale out)

2017-11-04 Thread James Briggs
> I know that Cassandra is built for scale out on commodity hardware The term "commodity hardware" is not very useful, though the averageserver-class machine bought in 2017 can work. Netflix found that SSD helped greatly with compactions in production.Generally servers use 10 GB networking in

[no subject]

2017-11-04 Thread vbhang...@gmail.com
Kishore, Here is the table dean and cfstats o/p --- === CREATE TABLE ks1.table1 ( key text, column1 'org.apache.cassandra.db.marshal.DynamicCompositeType(org.apache.cassandra.db.marshal.UTF8Type)', value blob, PRIMARY KEY (key, column1) ) WITH COMPACT

poolingOptions not serializable?

2017-11-04 Thread Andrea Giordano
Hi, I’m using datastax driver to use Cassandra as sink for some data streams with Apache Flink: I have a problem executing my application raising an error about the full queue. I discovered that the default value is 256, probably too low for my load, so I have raised it using poolingOptions