I am trying for the first time to use the cassandra-stress tool. Although I can run this tool, the output
the messages "Failed to connect via JMX, rather than collecting this data" are displayed,
Command
cassandra-stress user \ profile=./stress_write.yaml ops\(insert=1\) \ n=1000000 \ -log file=./stress_write.log \ -node node1,node2,node3,node4,node5,node6
Exit
WARN 19:44:25 Found host with 0.0.0.0 as rpc_address, using listen_address (/node5) to contact it instead. If this is incorrect you should avoid the use of 0.0.0.0 server side. WARN 19:44:25 Found host with 0.0.0.0 as rpc_address, using listen_address (/node1) to contact it instead. If this is incorrect you should avoid the use of 0.0.0.0 server side. WARN 19:44:25 Found host with 0.0.0.0 as rpc_address, using listen_address (/node2) to contact it instead. If this is incorrect you should avoid the use of 0.0.0.0 server side. WARN 19:44:25 Found host with 0.0.0.0 as rpc_address, using listen_address (/node4) to contact it instead. If this is incorrect you should avoid the use of 0.0.0.0 server side. WARN 19:44:25 Found host with 0.0.0.0 as rpc_address, using listen_address (/node3) to contact it instead. If this is incorrect you should avoid the use of 0.0.0.0 server side. WARN 19:44:26 Found host with 0.0.0.0 as rpc_address, using listen_address (/node5) to contact it instead. If this is incorrect you should avoid the use of 0.0.0.0 server side. WARN 19:44:26 Found host with 0.0.0.0 as rpc_address, using listen_address (/node1) to contact it instead. If this is incorrect you should avoid the use of 0.0.0.0 server side. WARN 19:44:26 Found host with 0.0.0.0 as rpc_address, using listen_address (/node2) to contact it instead. If this is incorrect you should avoid the use of 0.0.0.0 server side. WARN 19:44:26 Found host with 0.0.0.0 as rpc_address, using listen_address (/node4) to contact it instead. If this is incorrect you should avoid the use of 0.0.0.0 server side. WARN 19:44:26 Found host with 0.0.0.0 as rpc_address, using listen_address (/node3) to contact it instead. If this is incorrect you should avoid the use of 0.0.0.0 server side. INFO 19:44:26 Using data-center name 'DC2' for DCAwareRoundRobinPolicy (if this is incorrect, please provide the correct datacenter name with DCAwareRoundRobinPolicy constructor) INFO 19:44:26 New Cassandra host /node2:9042 added INFO 19:44:26 New Cassandra host /node5:9042 added Connected to cluster: MyCluster INFO 19:44:26 New Cassandra host /node4:9042 added INFO 19:44:26 New Cassandra host /node1:9042 added INFO 19:44:26 New Cassandra host /node6:9042 added Datatacenter: DC2; Host: /node4; Rack: rack1 Datatacenter: DC2; Host: /node3; Rack: rack1 Datatacenter: DC2; Host: /node6; Rack: rack1 Datatacenter: DC2; Host: /node5; Rack: rack1 Datatacenter: DC2; Host: /node1; Rack: rack1 Datatacenter: DC2; Host: /node2; Rack: rack1 INFO 19:44:26 New Cassandra host /node3:9042 added Created schema. Sleeping 6s for propagation. Failed to connect over JMX; not collecting these stats Generating batches with [1..1] partitions and [1..1] rows (of [1..1] total rows in the partitions) Failed to connect over JMX; not collecting these stats Failed to connect over JMX; not collecting these stats Improvement over 4 threadCount: 36% Failed to connect over JMX; not collecting these stats Improvement over 8 threadCount: 138% Failed to connect over JMX; not collecting these stats Improvement over 16 threadCount: 48% Failed to connect over JMX; not collecting these stats Improvement over 24 threadCount: 33% Failed to connect over JMX; not collecting these stats Improvement over 36 threadCount: 27% Failed to connect over JMX; not collecting these stats Improvement over 54 threadCount: 39% Failed to connect over JMX; not collecting these stats Improvement over 81 threadCount: 37% Failed to connect over JMX; not collecting these stats Improvement over 121 threadCount: 16% Failed to connect over JMX; not collecting these stats Improvement over 181 threadCount: 1% Failed to connect over JMX; not collecting these stats Improvement over 271 threadCount: 15% Failed to connect over JMX; not collecting these stats Improvement over 406 threadCount: 3% Failed to connect over JMX; not collecting these stats Improvement over 609 threadCount: -3%
Is there any command line or file configuration option that I need to specify for JMX? I tested and confirmed that the connection between the stress machine and my nodes is not a problem, because I was able to establish a connection between them through jmxsh.
Another exit problem, which may or may not be due to a JMX error, is that it lacks some key parts. I am quoting sample output on this Datastax documentation page to show parts that are missing from what I received:
WARNING: uncertainty mode (err<) results in uneven workload between thread runs, so should be used for high level analysis only Running with 4 threadCount Running WRITE with 4 threads until stderr of mean < 0.02 total ops , adj row/s, op/s, pk/s, row/s, mean, med, .95, .99, .999, max, time, stderr, gc:
Notes
- My cluster is running DSE 4.6.1 (Cassandra 2.0.12)
- I am running a stress tool from another machine.
- Stress Tool Version - From DS C 2.1 (Cassandra 2.1)