Will query on PK read entire partition?

If I have a table like this: PRIMARY KEY ((userid),deviceid) And I query SELECT * FROM devices where userid= ? and deviceid = ? Will cassandra read the entire partition for the userid? So if I lots of tombstones for userid, will they get scanned? I guess this depends on how the bloomfilter is w

TRUNCATE on a disk almost full - possible?

Hi all, We have a CF that's grown too large - it's not getting actively used in the app right now. The on-disk size of the . directory is ~407GB and I have only ~40GB free left on the disk. I understand that if I trigger a TRUNCATE on this CF, cassandra will try to take snapshot. My question: Is

Re: TRUNCATE on a disk almost full - possible?

Truncate needs no space. It just creates a hard link of all affected SSTables under the corresponding -SNAPSHOT dir (at least with default settings) and then removes the SSTables. Also this operation should be rather fast as it is mostly a file-deletion process with some metadata updates. 2017-04-

Re: TRUNCATE on a disk almost full - possible?

Hi Kunal, Timeout usually occured in the client (eg cqlsh), it does not mean that the truncate operation is interrupted. Have you checked that you have no old snapshot (automatic snaphost for instance) that you could get rid off to get some space back ? On 21 April 2017 at 11:27, benjamin roth

Re: Will query on PK read entire partition?

Hi Oskar, My guess (wait for confirmation maybe): When you read from a primary key + specific clustering key or (range of clustering keys), Apache Cassandra will look for these specific values and not read all the row. Yet it is important to know that a minimal block size of 64 KB is read from the

Cassandra Cluster Doubts

Hello! I have three DC: DC1 -> 3 nodes, Keyspace1:3 DC2 -> 3 nodes, Keyspace2:3 DCR1 -> 3 nodes, Keyspace1:2, Keyspace2:2 now I am trying to add a new datacenter to the cluster: DCR2-> 1 node (by now), Keyspace2:1 which network configuration can access to DC2 and DCR1 but it will never has a

Re: Drop tables takes too long

Hi, Problem is still not solved. Does anybody have any idea what to do with it? Thanks 2017-04-20 15:05 GMT+03:00 Bohdan Tantsiura : > Thanks Carlos, > > In each keyspace we also have 11 MVs. > > It is impossible to reduce number of tables now. Long GC Pauses take about > one minute. But why it

Re: Why are automatic anti-entropy repairs required when hinted hand-off is enabled?

Unfortunately, I don’t know much about the replication architecture. The only thing I know is that the replication is set at the keyspace level (i.e. 1, 2 or 3 or N replicas) and then there is the consistency level set at the client application level which determines how many acknowledgements ar

Re: Drop tables takes too long

Hi Bohdan, Carlos, Could you try some jvm tool to find out which thread are allocating memory or gc? maybe the migration stage thread.. BTW, is your cluster under high load while dropping table? As far as I remember, in older c* version, it applies the schema mutation in memory, ie. DROP, then f

Re: Cassandra Cluster Doubts

You have one cluster that is comprised of N nodes that may be distributed in racks and data centers. All the nodes of your cluster need to be able to communicate - they are one cluster. I think your options would be to a) establish network communication for the entire cluster, or b) set up a new c

Re: Cassandra Cluster Doubts

Hi Michael! Thanks for your answer I feared that was the answer...do you know if implementing my own Snitch would be possible to handle this situation? De: Michael Shuler en nombre de Michael Shuler Enviado: viernes, 21 de abril de 2017 19:16:43 Para: user@cass

Re: Downside to running multiple nodetool repairs at the same time?

The Spotify repo (https://github.com/spotify/cassandra-reaper) seems to not be maintained anymore. I'm not sure if they even support Cassandra 3.0 ( https://github.com/spotify/cassandra-reaper/issues/140). Regardless, in Cassandra 3.0 repairs are 1) Incremental, which means that the same SSTables

Re: Downside to running multiple nodetool repairs at the same time?

We (The Last Pickle) forked reaper a while ago and added support for 3.0. https://github.com/thelastpickle/cassandra-reaper We set up a mailing list here for Reaper specific questions: https://groups.google.com/forum/#!forum/tlp-apache-cassand