Re: Too High resident memory of cassandra 2.2.8

Hi Jeff, Below is the output of nodetool staus command. Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens OwnsHost ID Rack UN 192.168.68.156 *235.79 GB* 256 ? e7b1a44d-0cd2-4b60-b322-4f989933fc51 rack1 UN 192.168.68.15

Re: Too High resident memory of cassandra 2.2.8

Cassandra keeps certain data structures offheap, including bloom filters (scales with data size), compression metadata (scales with data size), and potentially memtables (scales with # of keyspaces/tables). How much data on your node? Onheap or offheap memtables? From: ankit tyagi

Re: cassandra python driver routing requests to one node?

We're using the "default" TokenAwarePolicy. Our nodes are spread across different racks within one datacenter. I've turned on debug logging for the Python driver, but it doesn't look like it logs which Casandra node each request goes to, but maybe I haven't got the right logging set to debug. On M

Too High resident memory of cassandra 2.2.8

Hi, we are using cassandra 2.2.8 version in production. we are seeing resident memory of cassndra process is very high 40G while heap size is only 8GB. root 23339 1 80 Nov11 ?2-09:38:08 /opt/java8/bin/java -ea -javaagent:bin/../lib/jamm-0.3.0.jar -XX:+CMSClassUnloadingEnabled -X

Re: cassandra python driver routing requests to one node?

What load balancing policies are you using in your client code ( https://datastax.github.io/python-driver/api/cassandra/policies.html)? Cheers Ben On Mon, 14 Nov 2016 at 16:22 Andrew Bialecki wrote: > We have an odd situation where all of a sudden of our cluster started > seeing a disproportion

cassandra python driver routing requests to one node?

We have an odd situation where all of a sudden of our cluster started seeing a disproportionate number of writes go to one node. We're using the Python driver version 3.7.1. I'm not sure if this is a driver issue or possibly a network issue causing requests to get routed in an odd way. It's not abs

Re: Problem with COPY FROM/TO and counters

Thanks for reporting this, I've opened CASSANDRA-12909 with all the details. You can apply the patch linked in that ticket if you want a quick workaround, but the root cause is still not fully understood. The reason why only counters are aff

Re: Consistency when adding data to collections concurrently?

Yeah, except I guess there's a minor debate left on whether it'd be more performant to store the labels in their own table, and do a read query each time when the parent item is fetched. Or if they should be kept as a set on the parent item and take the penalty when updating / deleting labels. (Wh

Re: Consistency when adding data to collections concurrently?

So problem solved! On Sun, Nov 13, 2016 at 1:37 PM, Ali Akhtar wrote: > Yeah, I am using set (not set though) > > On Sun, Nov 13, 2016 at 5:36 PM, DuyHai Doan wrote: > >> Yes you'd have to know the UDT values since it's part of the primary key >> to query your data. >> >> If I were you I would

Re: Consistency when adding data to collections concurrently?

Yeah, I am using set (not set though) On Sun, Nov 13, 2016 at 5:36 PM, DuyHai Doan wrote: > Yes you'd have to know the UDT values since it's part of the primary key > to query your data. > > If I were you I would stick to using a set and use UPDATE my_table > SET labels = labels + ; > > It does

Re: Consistency when adding data to collections concurrently?

Yes you'd have to know the UDT values since it's part of the primary key to query your data. If I were you I would stick to using a set and use UPDATE my_table SET labels = labels + ; It does work well with concurrent updates. On Sun, Nov 13, 2016 at 1:32 PM, Ali Akhtar wrote: > But then how w

Re: Consistency when adding data to collections concurrently?

But then how would you query it? You'd need to know all the values of the udt, right? On Sun, Nov 13, 2016 at 5:30 PM, DuyHai Doan wrote: > "Also can you make a UDT a clustered key?" --> yes if it's frozen > > On Sun, Nov 13, 2016 at 1:25 PM, Ali Akhtar wrote: > >> If I wanted to get all values

Re: Consistency when adding data to collections concurrently?

"Also can you make a UDT a clustered key?" --> yes if it's frozen On Sun, Nov 13, 2016 at 1:25 PM, Ali Akhtar wrote: > If I wanted to get all values for an item, including its labels, how would > that be done in the above case? > > Also can you make a UDT a clustered key? > > On Sun, Nov 13, 201

Re: Consistency when adding data to collections concurrently?

If I wanted to get all values for an item, including its labels, how would that be done in the above case? Also can you make a UDT a clustered key? On Sun, Nov 13, 2016 at 4:33 AM, Manoj Khangaonkar wrote: > Hi, > > Instead of using a collection, consider making label a clustered column. > > Wi