Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 14 Feb 2012 13:50:59 +0000 (UTC)
From: "Jonathan Ellis (Commented) (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <1912053147.36332.1329227459595.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2103209779.25767.1319739752526.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-3412) make nodetool ring ownership
 smarter
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Ellis commented on CASSANDRA-3412:
-------------------------------------------

bq. If there are multiple keyspaces, leave the percentage undefined unless the user selects keyspace

I think we can do a little better than that -- we only have to leave ownership undefined if the KS actually have different replication settings.

bq. The main problem I think is that it's not clear how to make the user realize why he's not getting ownership information.

Shrug, I don't have a problem with just printing out a line explaining why, at the bottom.
                
> make nodetool ring ownership smarter
> ------------------------------------
>
>                 Key: CASSANDRA-3412
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3412
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Jackson Chung
>            Assignee: Vijay
>            Priority: Minor
>
> just a thought.. the ownership info currently just look at the token and calculate the % between nodes. It would be nice if it could do more, such as discriminate nodes of each DC, replica set, etc. 
> ticket is open for suggestion...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira