cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaakko Laine (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CASSANDRA-698) ClusterProbe
Date Wed, 20 Jan 2010 06:17:57 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12802697#action_12802697
] 

Jaakko Laine commented on CASSANDRA-698:
----------------------------------------

What kind of division did you have in mind? Division on class-level or a division to separate
tools?

NodeProbe is getting bloated (just added two new commands, #723), so something should be done
about it. I think it might be beneficial to have one single "nodeprobe" command for all tasks
at least for now, but if there is natural division between commands, then two tools might
be better.

> 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
>
>
> 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.


Mime
View raw message