cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jaakko Laine (JIRA)" <>
Subject [jira] Commented: (CASSANDRA-698) ClusterProbe
Date Thu, 21 Jan 2010 13:46:54 GMT


Jaakko Laine commented on CASSANDRA-698:

Yep, having things separated is good. Just thinking whether having two tools for related things
is good or bad in the end. Many commands are "obviously" either node or cluster specific,
but some are not. removetoken for instance affects the whole cluster but it is in nodeprobe.
If there are two tools for related things, some admins are going to curse us when they have
to remember which one to use for particular task :-) But we can have two tools, not a problem
for me.

> ClusterProbe
> ------------
>                 Key: CASSANDRA-698
>                 URL:
>             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,
> 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.

View raw message