Re: repair in C* 3.11.2 and anticompactions

Hey Jean, I think it still does anticompaction by default regardless, it will not do so only if you do subrange repair. TLP wrote a pretty good article on that: http://thelastpickle.com/blog/2017/12/14/should-you-use-incremental-repair.html On 24 May 2018 at 00:42, Jean Carlo

Re: estimated number of keys vs ttl

I believe that key estimates won't immediately respond to expired TTL, Not until after compaction has completely dropped the records (which will include subtle logic related to gc_grace and partitions with data in multiple SSTables). On Wed, May 23, 2018 at 6:18 AM Rahul Singh

Snapshot SSTable modified??

Hi Everyone, We’ve noticed a few times in the last few weeks that when we’re doing backups, tar has complained with messages like this: tar: /var/lib/cassandra/data/mars/test_instances_by_test_id-6a9440a04cc111e8878675f1041d7e1c/snapshots/backup_20180523_024502/mb-63-big-Data.db: file changed

unsubscribe

Thanks, Hitesh dua hiteshd...@gmail.com

Re: estimated number of keys vs ttl

If the TTL actually reduces the key count , should. It’s possible to TTL a row from a partition but not the whole partition. 1 key = 1 partition != 1 row != 1 cell -- Rahul Singh rahul.si...@anant.us Anant Corporation On May 23, 2018, 6:07 AM -0500, Grzegorz Pietrusza ,

estimated number of keys vs ttl

Hi I'm using tablestats to get estimated number of partitioning keys. In my case all writes are done with TTL of a few days. Is the key count decreased when TTL hits? Regards Grzegorz

Re: Using K8s to Manage Cassandra in Production

Using a statefulset should get you pretty far, though will likely be less effective than a coreos-style “operator”. Some random points: For scale-up: a node shouldn’t report “ready” until it’s in the NORMAL state; this will prevent multiple nodes from bootstrapping at once. For scale-down: as of

Re: Snapshot SSTable modified??

In versions before 3.0, sstables were written with a -tmp filename and copied/moved to the final filename when complete. This changes in 3.0 - we write into the file with the final name, and have a journal/log to let uss know when it's done/final/live. Therefore, you can no longer just watch for

Re: Using K8s to Manage Cassandra in Production

Why did you choose java for the operator implementation when everybody seems to use the go client (probably for greater functionalities) ? 2018-05-23 15:39 GMT+02:00 Ben Bromhead : > You can get a good way with StatefulSets, but as Tom mentioned there are > still some

repair in C* 3.11.2 and anticompactions

Hello I just want to understand why, if I run a repair non incremental like this nodetool -h 127.0.0.1 -p 7100 repair -full -pr keyspace1 standard1 Cassandra does anticompaction as the logs show INFO [CompactionExecutor:20] 2018-05-23 16:36:27,598 CompactionManager.java:1545 - Anticompacting

Re: Using K8s to Manage Cassandra in Production

You can get a good way with StatefulSets, but as Tom mentioned there are still some issues with this, particularly around scaling up and down. We are working on an Operator for Apache Cassandra, you can find it here https://github.com/instaclustr/cassandra-operator. This is a joint project

Re: Using K8s to Manage Cassandra in Production

Here is the expectations around compatibility levels https://github.com/kubernetes/community/blob/master/contributors/design-proposals/api-machinery/csi-new-client-library-procedure.md#client-capabilities Though references to gold, silver, bronze etc seem to have largely gone away... not sure

Re: Using K8s to Manage Cassandra in Production

Thanks ! Do you have some pointers on the available features ? I am more afraid of the lack of custom controller integration, for instance the code generator... 2018-05-23 17:17 GMT+02:00 Ben Bromhead : > The official Kubernetes Java driver is actually pretty feature

Re: Using K8s to Manage Cassandra in Production

The official Kubernetes Java driver is actually pretty feature complete, if not exactly idiomatic Java... it's only missing full examples to get it to GOLD compatibility levels iirc. A few reasons we went down the Java path: - Cassandra community engagement was the primary concern. If you

Anyone try out C* with latest Oracle JDK update?

Hi, Any experiences any one have running C* 3.x with the Oracle JDK update 1.8 u172 / u171 that came out mid-April? Thanks, Sam - To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org For additional commands, e-mail: