nodetool gossipinfo question

Hi – I have a question on the significance a particular attribute in the output result for ‘nodetool gossipinfo’: RELEASE_VERSION. We have a node that is periodically crashing with nothing really of significance in the logs and we’re trying to ascertain if it’s an OS issue or something to do

timeoutexceptions with UDF causing cassandra forceful exits

Hi – Is it normal for cassand to be shutdown forcefully on timeout exceptions when using UDFs? We are admittedly trying some load tests on our dev environments which may be somewhat constrained, but didn’t expect to see forceful shutdowns such as these when we ran our tests. We’re running

Re: EC2 instance recommendations

nces. Cheers. On 23-05-2017 21:39, sfesc...@gmail.com<mailto:sfesc...@gmail.com> wrote: I think this is overstating it. If the instance ever stops you'll lose the data. That means if the server crashes for example, or if Amazon decides your instance requires maintenance. On Tue,

Re: EC2 instance recommendations

at a reasonable rate, it gets more expensive than an I3. From: Jonathan Haddad <j...@jonhaddad.com> Date: Tuesday, May 23, 2017 at 9:42 AM To: "Gopal, Dhruva" <dhruva.go...@aspect.com>, Matija Gobec <matija0...@gmail.com>, Bhuvan Rawal <bhu1ra...@gmail.com> Cc:

Re: EC2 instance recommendations

and is TTL’d after. From: Matija Gobec <matija0...@gmail.com> Date: Tuesday, May 23, 2017 at 8:15 AM To: Bhuvan Rawal <bhu1ra...@gmail.com> Cc: "Gopal, Dhruva" <dhruva.go...@aspect.com>, "user@cassandra.apache.org" <user@cassandra.apache.org> Subject: Re:

EC2 instance recommendations

Hi – We’ve been running M4.2xlarge EC2 instances with 2-3 TB of storage and have been comparing this to I-3.2xlarge, which seems more cost effective when dealing with this amount of storage and from an IOPS perspective. Does anyone have any recommendations/ on the I-3s and how it performs

Re: cassandra 3.10

for Cassandra and are concerned that there may be other issues with the 3.10 release and maybe we should hold off till 3.11 is released and ready. Any opinions/feedback will help. Regards, Dhruva From: Anthony Grasso <anthony.gra...@gmail.com> Date: Thursday, May 11, 2017 at 5:06 PM To: "Go

Re: repair question (-dc option)

May 11, 2017 at 1:33 PM To: "Gopal, Dhruva" <dhruva.go...@aspect.com> Cc: "user@cassandra.apache.org" <user@cassandra.apache.org> Subject: Re: repair question (-dc option) If there was no node down during that period, and you are using LOCAL_QUORUM read/write, then ye

repair question (-dc option)

Hi – I have a question on running a repair after bringing up a node that was down (brought down gracefully) for a few days within a data center. Can we just run nodetool repair –dc on a single node (within that DC – specifically the downed node, after it is brought online) and have that

cassandra 3.10

Hi – We’re currently on 3.9 and have been told that Cassandra 3.10 is a more stable version to be on. We’ve been using the datastax-ddc rpms in our production and dev environments (on 3.9) and it appears there is no 3.10 rpm version out yet. We tried to build our own rpm (our devops processes

Re: cassandra OOM

a.apache.org>> Date: Monday, April 3, 2017 at 8:00 AM To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>" <user@cassandra.apache.org<mailto:user@cassandra.apache.org>> Subject: Re: cassandra OOM Hi, could you share your GC settings ? G1 or CMS ? Heap size, e

Re: cassandra OOM

t; Reply-To: "user@cassandra.apache.org" <user@cassandra.apache.org> Date: Monday, April 3, 2017 at 8:00 AM To: "user@cassandra.apache.org" <user@cassandra.apache.org> Subject: Re: cassandra OOM Hi, could you share your GC settings ? G1 or CMS ? Heap size, etc... Than

cassandra OOM

Hi – We’ve had what looks like an OOM situation with Cassandra (we have a dump file that got generated) in our staging (performance/load testing environment) and I wanted to reach out to this user group to see if you had any recommendations on how we should approach our investigation as to

Digest mismatch

I’m running into a situation where I’m seeing a lot of Digest errors in the debug log. I looked at this post: http://stackoverflow.com/questions/39765813/datastax-mismatch-for-key-issue and verified that read_repair_chance is set to 0. We are using DateTieredCompactionStrategy for our time

Re: Trying to identify the cause of these errors.

Any suggestions/recommendations? Anything will help at this point. Thanks! Regards, DHRUVA GOPAL sr. MANAGER, ENGINEERING REPORTING, ANALYTICS AND BIG DATA +1 408.325.2011 WORK +1 408.219.1094 MOBILE UNITED STATES dhruva.go...@aspect.com

Trying to identify the cause of these errors.

My colleague (Richard Ney) has already been in touch with you on a couple of other issues we’ve seen in the past. Our development been trying to track down some new issues we’ve been seeing on one of our pre-prod environments where we’ve been having consistent failures very often (every day or