Unsubscribe

Hi It was great to be part of this group. Thanks for helping out. Please unsubscribe me now. Regards, Malay Nilabh BIDW BU/ Big Data CoE L&T Infotech Ltd, Hinjewadi,Pune [cid:image001.gif@01CFF80D.D1C29F90]: +91-20-66571746 [cid:image002.png@01CFF80D.D1C29F90]+91-73-879-00727 Email: malay.nil...

Re: new data not flushed to sstables

On Mon, Nov 3, 2014 at 7:44 AM, Sebastian Martinka < sebastian.marti...@mercateo.com> wrote: > System and Keyspace Information: > > 4 Nodes > > > CREATE KEYSPACE restore_test WITH replication = { 'class': > 'SimpleStrategy', > > 'replication_factor': '3'}; > > > > > > I assumed, that a flush

Re: Client-side compression, cassandra or both?

I wouldn’t do both. Unless a little server CPU or (and you’d have to measure it - I imagine it is probably not significant - as you say C* has more context, and hopefully most things can compress “0, “ repeatedly) disk space are an issue, I wouldn’t bother to compress yourself. Compression acros

Re: Netstats > 100% streaming

Thanks Mark, that does seem like the right ticket. Thanks for the info, I wasn't successful finding that =) On Mon, Nov 3, 2014 at 5:00 AM, Mark Reddy wrote: > HI Eric, > > It looks like you are running into CASSANDRA-7878 > which is fixed

new data not flushed to sstables

System and Keyspace Information: 4 Nodes Cassandra 2.0.9 cqlsh 4.1.1 CQL spec 3.1.1 Thrift protocol 19.39.0 java version "1.8.0_20" Java(TM) SE Runtime Environment (build 1.8.0_20-b26) Java HotSpot(TM) 64-Bit Server VM (build 25.20-b23, mixed mode) CREATE KEYSPACE restore_test WITH replication =

Re: Client-side compression, cassandra or both?

Hello Robin You have many options for compression in C*: 1) Serialized in bytes instead of JSON, to save a lot of space due to String encoding. Of course the data will be opaque and not human readable 2) Activate client-node data compression. In this case, do not forget to ship LZ4 or SNAPPY de

Client-side compression, cassandra or both?

Hi there, We're working on a project which is going to store a lot of JSON objects in Cassandra. A large piece of this (90%) consists of an array of integers, of which in a lot of cases there are a bunch of zeroes. The average JSON is 4KB in size, and once GZIP (default compression) just under 10

Re: Netstats > 100% streaming

HI Eric, It looks like you are running into CASSANDRA-7878 which is fixed in 2.0.11 / 2.1.1 Mark On 1 November 2014 14:08, Eric Stevens wrote: > We've been commissioning some new nodes on a 2.0.10 community edition > cluster, and we're se