Mailing-List: contact cassandra-commits-help@incubator.apache.org;
 run by ezmlm
Precedence: bulk
Reply-To: cassandra-dev@incubator.apache.org
Message-ID: <1725994022.394681264081614622.JavaMail.jira@brutus.apache.org>
Date: Thu, 21 Jan 2010 13:46:54 +0000 (UTC)
From: "Jaakko Laine (JIRA)" <jira@apache.org>
To: cassandra-commits@incubator.apache.org
Subject: [jira] Commented: (CASSANDRA-698) ClusterProbe
In-Reply-To: <209322085.229411263431814440.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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