Re: Right way to stress a cassandra cluster

The right way to test it is with the key space and table matching the schema/load you intend to use in production -- Jeff Jirsa > On Nov 30, 2017, at 8:53 PM, Akshit Jain wrote: > > Hi, > Is it right to load test the cassandra cluster using stress tool with default

Right way to stress a cassandra cluster

Hi, Is it right to load test the cassandra cluster using stress tool with default keyspace, keyspace1 and having columns type as blob?

Tools to analyze Gc pauses.

Hi, I am seeing couple of gc pauses on nodes causing issue, in my environment we are using 36 nodes cluster using g1gc garbage collector with heap 24gb, having couple of wide partitions which are around 250 mb, not sure if this is an as issue as heap size is 24 gb. I agree it will not be

Re: Best JMX Monitor to graphite ?

On Wed, Nov 29, 2017 at 3:18 PM, Tobias Eriksson wrote: > Hi > > I would like to monitor my Cassandra cluster looking at the JMX beans and > transfer stats to Graphite. > > I have done some googling and some suggest using jmxtrans, and some has > moved on to

Re: can't reach cassandra outside my lan

just tried, without results. telnet my_ip 9042 returns connection refused and lsof -n -i4TCP:9042 | grep LISTEN returns no output > On 30 Nov 2017, at 19:42, Jon Haddad wrote: > > Cassandra is listening on your localhost address, 127.0.0.1, not your > laptop’s address on

Re: Node crashes on repair (Cassandra 3.11.1)

That was worded poorly. The depth has a max depth of 20, the tree is the same size for any range > 2**20. On Thu, Nov 30, 2017 at 10:43 AM, Jeff Jirsa wrote: > Merkle trees have a fixed size/depth (2**20), so it’s not that, but it > could be timing out elsewhere (or still

Re: Node crashes on repair (Cassandra 3.11.1)

Merkle trees have a fixed size/depth (2**20), so it’s not that, but it could be timing out elsewhere (or still running validation or something) -- Jeff Jirsa > On Nov 30, 2017, at 10:12 AM, Javier Canillas > wrote: > > Christian, > > I'm not an expert, but maybe

Re: can't reach cassandra outside my lan

Cassandra is listening on your localhost address, 127.0.0.1, not your laptop’s address on the network. Set rpc_address to the address on your network, or use rpc_interface and let Cassandra figure it out. > On Nov 30, 2017, at 10:38 AM, Andrea Giordano > wrote:

can't reach cassandra outside my lan

Hi, osx user here. I have installed a simple Cassandra db on my laptop and I would like to query it outside the Lan. So I set port forwarding and port triggering on my router (vodafone station) to link external 9042 to internal 9042. Moreover I set on cassandra.yaml the broadcast_rpc_address to

Re: Node crashes on repair (Cassandra 3.11.1)

Christian, I'm not an expert, but maybe the merkle tree is too big to transfer between nodes and that's why it times out. How many nodes do you have and what's the size of the keyspace? Have you ever done a successfully repair before? Cassandra reaper does repair based on tokenrange (or even

Re: Schema version mismatch with 3.0.8 and 3.0.14

I guess I didn’t realize you were adding and upgrading s at the same time Do one or the other first (either add the new node at the old version, or upgrade to the new version and then add the new node), or use the two step process described in 13004 -- Jeff Jirsa > On Nov 30, 2017, at 9:40

Re: Schema version mismatch with 3.0.8 and 3.0.14

Hello Jeff, I tried with 3.0.15 as well and I see the same issue. Here are the steps I followed. 1. I have a 3 node C* cluster with 3.0.8 version 2. Added a new node (4th) node with 3.0.15 version of cassandra 3. New node joins the cluster but it is creates it's own schema and don't bootstrap

Re: gc causes C* node hang

Mail client may be changing changing the char if your copy and pasting, its - "hyphen" not the unicode en dash –. I would recommend adding it to jvm options like oleksandr pointed out Chris On Thu, Nov 30, 2017 at 1:50 AM, Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > On Thu, Nov

Node bootstrap error

Hello, Am adding a new node to a cluster, bootstrap failed with the following errors: WARN [STREAM-IN-/111.11.11.193] 2017-11-30 04:44:05,825 CompressedStreamReader.java:119 - [Stream c9d90a60-d56f-11e7-a95c-39e84a08567f] Error while reading partition null from stream on ks='system_auth' and

Node crashes on repair (Cassandra 3.11.1)

Hello, after updating our cluster to Cassandra 3.11.1 (previously 3.9) running a ‘nodetool repair –full’ leads to the node crashing. Logfile showed the following Exception: ERROR [ReadRepairStage:36] 2017-11-30 07:42:06,439 CassandraDaemon.java:228 - Exception in thread