4f275cc44b
The describeRingJMX method, returns a formated output. The output should be similiar to origin as oppose to the current implementation that returns a json representation. After the change an example of nodetool describering: $ nodetool describering keyspace1 Schema Version:1074c31b-1f39-3df2-90ff-7f0b64bb3ea4 TokenRange: TokenRange(start_token:7485973865401664349, end_token:-338297331236877217, endpoints:[127.0.0.1], rpc_endpoints:[127.0.0.1], endpoint_details:[EndpointDetails(host:127.0.0.1, datacenter:datacenter1, rack:rack1)]) TokenRange(start_token:-338297331236877217, end_token:7485973865401664349, endpoints:[127.0.0.2], rpc_endpoints:[127.0.0.2], endpoint_details:[EndpointDetails(host:127.0.0.2, datacenter:datacenter1, rack:rack1)]) On sycall-jmx: Fixes #21 Signed-off-by: Amnon Heiman <amnon@scylladb.com> |
||
---|---|---|
.. | ||
db | ||
gms | ||
locator | ||
metrics | ||
net | ||
repair | ||
service | ||
streaming |