[
https://issues.apache.org/jira/browse/CASSANDRA-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803063#action_12803063
]
Eric Evans commented on CASSANDRA-698:
--------------------------------------
Alright, the current round of patches (v3), refactors all of
application-specific code into a new class (NodeCmd) which the `nodeprobe'
script now uses. It's all transparent to the end-user, but it leaves NodeProbe
scoped as a high-level JMX client for cassandra nodes.
The last two patches adds endpoint fetching to NodeProbe and ports Chris's
ClusterProbe (renamed to ClusterCmd to be consistent with NodeCmd) to use
NodeProbe. It works exactly as before, but has less code/doesn't duplicated
code with NodeProbe.
I even wrote a shell wrapper...
bin/clustertool -host localhost get_endpoints canhasendpoint
Key : canhasendpoint
Endpoints : [localhost/127.0.0.1]
> ClusterProbe
> ------------
>
> Key: CASSANDRA-698
> URL: https://issues.apache.org/jira/browse/CASSANDRA-698
> Project: Cassandra
> Issue Type: New Feature
> Components: Tools
> Reporter: Chris Goffinet
> Assignee: Chris Goffinet
> Priority: Minor
> Fix For: 0.7
>
> Attachments:
> 0001-Added-ClusterProbe.-Supports-get_endpoints-key.patch,
> v3-0001-CASSANDRA-698-NodeProbe-refactor-move-main-to-new-clas.txt,
> v3-0002-NodeProbe-refactor-move-print-methods-to-new-class.txt,
> v3-0003-add-new-getEndPoints-method.txt,
> v3-0004-add-clustercmd-tool-currently-only-prints-endpoints.txt
>
>
> I'd like to introduce ClusterProbe, for situations where you want to find
> information at cluster level. The first operation is get_endpoints, where you
> can supply a key. I want to also add support for showing hit ratio for column
> families at cluster level.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
