But monitoring cassandra with jmx using jvisualVM shows no problem, less than 30% of heap size used
Sent using Zoho Mail ---- On Sun, 18 Feb 2018 17:26:59 +0330 Rahul Singh <[email protected]> wrote ---- You don’t don’t have enough memory. That’s just a start. -- Rahul Singh [email protected] Anant Corporation On Feb 18, 2018, 6:29 AM -0500, onmstester onmstester <[email protected]>, wrote: I've configured a simple cluster using two PC with identical spec: cpu core i5 RAM: 8GB ddr3 Disk: 1TB 5400rpm Network: 1 G (I've test it with iperf, it really is!) using the common configs described in many sites including datastax itself: cluster_name: 'MyCassandraCluster' num_tokens: 256 seed_provider: - class_name: org.apache.cassandra.locator.SimpleSeedProvider parameters: - seeds: "192.168.1.1,192.168.1.2" listen_address: rpc_address: 0.0.0.0 endpoint_snitch: GossipingPropertyFileSnitch Running stress tool: cassandra-stress write n=1000000 -rate threads=1000 -mode native cql3 -node 192.168.1.1,192.168.1.2 Over each node it shows 39 K writes/seconds, but running the same stress tool command on cluster of both nodes shows 45 K writes/seconds. I've done all the tuning mentioned by apache and datastax. There are many use cases on the net proving Cassandra linear Scalability So what is wrong with my cluster? Sent using Zoho Mail
