Jon Haddad created CASSANDRA-20082:
--------------------------------------
Summary: nodetool proxyhistograms errors out
Key: CASSANDRA-20082
URL: https://issues.apache.org/jira/browse/CASSANDRA-20082
Project: Cassandra
Issue Type: Bug
Reporter: Jon Haddad
I have a test cluster running 5.0.2 which has been running for several hours.
The cluster is up and running and has accepted 300MM writes.
{noformat}
ubuntu@cassandra0:~$ nt status
Datacenter: us-west-2
=====================
Status=Up/Down
|/ State=Normal/Leaving/Joining/Moving
-- Address Load Tokens Owns (effective) Host ID
Rack
UN 10.0.2.4 499.57 GiB 4 100.0%
ac8ef372-d2a9-4d34-9c05-98f2c61d6a5d us-west-2c
UN 10.0.1.96 501.59 GiB 4 100.0%
82762ee1-3d72-4a22-8b7c-b6da20d5f836 us-west-2b
UN 10.0.0.100 502.24 GiB 4 100.0%
94bacb9f-f568-4091-85fb-b0a67ece6d13 us-west-2a
{noformat}
I bumped into this when trying to get an idea of the node's latency:
{noformat}
ubuntu@cassandra0:~$ nt proxyhistograms
Exception in thread "main" java.lang.IllegalArgumentException: Server is not
initialized yet, cannot run nodetool.
at org.apache.cassandra.tools.NodeTool.err(NodeTool.java:319)
at org.apache.cassandra.tools.NodeTool.execute(NodeTool.java:282)
at org.apache.cassandra.tools.NodeTool.main(NodeTool.java:85)
{noformat}
I haven't been able to reproduce this locally yet.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
