cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Wojciech Meler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6054) cluster availability report
Date Wed, 18 Sep 2013 13:16:57 GMT

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

Wojciech Meler commented on CASSANDRA-6054:
-------------------------------------------

I'm not sure if replica placement strategy details are/should be available on JMX.

I thought that nodetool is right place for such feature as Cassandra JMX API would evolve.
                
> cluster availability report
> ---------------------------
>
>                 Key: CASSANDRA-6054
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6054
>             Project: Cassandra
>          Issue Type: Wish
>            Reporter: Wojciech Meler
>
> It would be nice to have a way to check cassandra cluster status in terms of availablilty
for operations on keyspace at given consistency level.
> Such operation should output information in availbility matrix where dimensions are:
> - consistency level
> - datacenter
> and values are percent of ring available in DC at given consistency level, f.e.:
> consistency level                  | DC1  | DC2 
> CL.One                             | 100% | 100% 
> CL.LocalQuorum                     | 95%  | 100%
> CL.All                             | 90%  | 90%
> Unfortunatelly c* don't have CL.LocalAll, so DC split in last line have limited sense
;).
> It is valuable information for operations teams.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message