[
https://issues.apache.org/jira/browse/CASSANDRA-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800387#action_12800387
]
Chris Goffinet commented on CASSANDRA-698:
------------------------------------------
Right, but the reason why I started this was because
a) I wanted a way to hit a cluster of nodes without needing a storage-conf file
b) Start the foundation of other commands (including global snapshot that is
coming up)
It could go in nodeprobe, but just didn't feel right to be there.
I still think getEndPoints could live in clusterprobe, as I saw nodeprobe just
pertaining to a single node functionality. Since ClusterProbe is more in line
with finding information about a cluster (multiple nodes) I thought it made for
sense here.
Yeah I can add getLiveNaturalEndpoints if I missed that :)
> 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.
