Re: Lot of GC on two nodes out of 7

Hi Anishek, In addition to the good advice others have given, do you notice any abnormally large partitions? What does cfhistograms report for 99% partition size? A few huge partitions will cause very disproportionate load on your cluster, including high GC. --Bryan On Wed, Mar 2, 2016 at 9:28

Re: Broken links in Apache Cassandra home page

On Thu, Mar 3, 2016 at 10:10 AM, Eric Evans wrote: >> https://www.w3.org/Addressing/draft-mirashi-url-irc-01.txt >> >> irc://freenode.net/#cassandra > > Hrmm, that seems like more of a candidate for a channel name link, no? > For example: > > Many of the Cassandra

Modeling transactional messages

Hi everyone, Can anyone please let me know if I am heading to an antiparttern or somethingelse bad? How would you model the following ... ? I am migrating from MYSQL to Cassandra, I have a scenario in which need to store the content of "to be sent" transactional email messages that the

Re: Lot of GC on two nodes out of 7

Hello, Bryan, most of the partition sizes are under 45 KB I have tried with concurrent_compactors : 8 for one of the nodes still no improvement, I have tried max_heap_Size : 8G, no improvement. I will try the newHeapsize of 2G though i am sure CMS will be a longer then. Also doesn't look like

Re: Lot of GC on two nodes out of 7

I’d personally would have gone the other way – if you’re seeing parnew, increasing new gen instead of decreasing it should help drop (faster) rather than promoting to sv/oldgen (slower) ? From: Anishek Agarwal Reply-To: "user@cassandra.apache.org" Date: Thursday, March 3, 2016 at 8:55 PM

Re: Removing Node causes bunch of HostUnavailableException

What is the exact exception you are getting and where do you get it? Is it UnavailableException or NoHostAvailableException and does it occur on the client, using the Java driver? What is your LoadBalancingPolicy? What consistency level is the client using? What retry policy is the client

Re: Consistent read timeouts for bursts of reads

Emils, I realize this may be a big downgrade, but are you timeouts reproducible under Cassandra 2.1.4? Mike On Thu, Feb 25, 2016 at 10:34 AM, Emīls Šolmanis wrote: > Having had a read through the archives, I missed this at first, but this > seems to be *exactly* like

Re: MemtableReclaimMemory pending building up

Hi Dan, I'll try to go through all the elements: seeing this odd behavior happen, seemingly to single nodes at a time Is that one node at the time or always on the same node. Do you consider your data model if fairly, evenly distributed ? The node starts to take more and more memory (instance

Re: Broken links in Apache Cassandra home page

On Wed, Mar 2, 2016 at 1:55 PM, Robert Coli wrote: > On Wed, Mar 2, 2016 at 7:00 AM, Eric Evans wrote: >> >> On Tue, Mar 1, 2016 at 8:30 PM, ANG ANG wrote: >> > "#cassandra channel": http://freenode.net/ >> >> The latter, while

Re: how to read parent_repair_history table?

> is there any other better way to find out a node's token range? I see systems.peers column family seems to include range information, so that is promising but when I look at both datastax java driver and python driver, its API both require a keyspace name and host name, I wonder why ? range

Re: Removing Node causes bunch of HostUnavailableException

Thanks Alain for quick and detailed response. My answers inline. One thing I want to clarify is, the nodes got recycled due to some automatic health check failure. This means old nodes are dead and new nodes got added w/o our intervention. So replacing nodes would not work for us since the new

Re: Removing Node causes bunch of HostUnavailableException

Which node(s) were getting the HostNotAvailable errors - all nodes for every query, or just a small portion of the nodes on some queries? It may take some time for the gossip state to propagate; maybe some of it is corrupted or needs a full refresh. Were any of the seed nodes in the collection

Re: Removing Node causes bunch of HostUnavailableException

Hi Jack, Which node(s) were getting the HostNotAvailable errors - all nodes for every query, or just a small portion of the nodes on some queries? Not all read/writes are failing with Unavalable or Timeout exception. Writes failures were around 10% of total calls. Reads were little worse (as