cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "mike li (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-3416) nodetool and show schema give different value for compact threshold
Date Fri, 28 Oct 2011 15:01:33 GMT
nodetool and show schema give different value for compact threshold
-------------------------------------------------------------------

                 Key: CASSANDRA-3416
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3416
             Project: Cassandra
          Issue Type: Bug
          Components: Tools
    Affects Versions: 1.0.0
         Environment: ALL
            Reporter: mike li
            Priority: Minor


On Thu, Oct 27, 2011 at 10:06 PM,  <mike.li@thomsonreuters.com> wrote:
> Why these two gives different results?
> ./nodetool -h 172.xx.xxx.xx  getcompactionthreshold Timeseries TickData

> Current compaction thresholds for Timeseries/TickData:
>
> min = 1,  max = 2147483647
>

>
> [default@Timeseries] show schema;

>
> use Timeseries;
>
> ...
>
>   and min_compaction_threshold = 4
>
>   and max_compaction_threshold = 32
>

>
> If we use leveledCompaction, does compaction threshold setting matter?
>

No, it doesn't matter with leveled compaction. The code override the min threshold to 1 and
the max to Integer.MAX_VALUE, which is what you are seeing with nodetool.
It obviously don't override it everywhere it should, given the output of show schema.

Do you mind opening a JIRA ticket so we fix it?

--
Sylvain

>

>


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

        

Mime
View raw message