cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CASSANDRA-5783) nodetool and cassandra-cli report different information for "Compaction min/max thresholds"
Date Sat, 20 Jul 2013 23:04:49 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-5783?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis resolved CASSANDRA-5783.
---------------------------------------

    Resolution: Not A Problem

cli is reporting the schema, which has not been modified, only temporarily overridden.
                
> nodetool and cassandra-cli report different information for "Compaction min/max thresholds"
> -------------------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-5783
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-5783
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Tools
>    Affects Versions: 1.2.6
>            Reporter: Peter Haggerty
>            Priority: Minor
>
> Ask cassandra-cli and nodetool the same question and get different answers back. This
was executed after using nodetool to adjust the compactionthreshold on this CF to have a minimum
of 2. The change was observed to work as we saw increased compactions which is exactly what
one would expect
> $ echo "describe ${CF};" \
>   | cassandra-cli -h localhost -k ${KEYSPACE} \
>   | grep thresholds
>       Compaction min/max thresholds: 4/32
> $ nodetool -h localhost getcompactionthreshold ${KEYSPACE} ${CF}
> Current compaction thresholds for Metrics/dimensions_active_1:
>  min = 2,  max = 32

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