[
https://issues.apache.org/jira/browse/CASSANDRA-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800374#action_12800374
]
Eric Evans commented on CASSANDRA-698:
--------------------------------------
Isn't this still technically still a node operation, (i.e. it is the end-points
according to some node)? This doesn't seem much different in scope to the
`ring' sub-command of NodeProbe.
Originally, I had intended for NodeProbe to be a class to abstract all of the
tedious JMX-related boilerplate, allowing other applications (be they node or
cluster in scope), to be built upon it. I stuck a main() on it mainly so that
we'd have *something*. In retrospect, that was probably a mistake.
Would it make sense to move the getEndPoints(key) method to NodeProbe, and
refactor all of the other stuff (the stuff there in support of a console
application) into another class(es)?
FYI, I think this patch is missing the addition of
getLiveNaturalEndpoints(String key) to StorageServiceMBean.
> ClusterProbe
> ------------
>
> Key: CASSANDRA-698
> URL: https://issues.apache.org/jira/browse/CASSANDRA-698
> Project: Cassandra
> Issue Type: New Feature
> Affects Versions: 0.9
> Reporter: Chris Goffinet
> Assignee: Chris Goffinet
> Priority: Minor
> Fix For: 0.9
>
> Attachments: 0001-Added-ClusterProbe.-Supports-get_endpoints-key.patch
>
>
> 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.
