cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex Zarutin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-3416) nodetool and show schema give different value for compact threshold
Date Tue, 02 Jul 2013 20:09:22 GMT

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

Alex Zarutin updated CASSANDRA-3416:
------------------------------------

    Attachment: CASSANDRA-3416.txt

Tested this issue using default SizeTieredCompactionStrategy and LeveledCompactionStrategy
compaction strategies. Result (for both tests) is the same:

NODETOOL:
$> /Users/alexzarutin/.ccm/test-1.2.6/node1/bin/nodetool  --host localhost --port 7100
getcompactionthreshold Keyspace1 Standard1
Current compaction thresholds for Keyspace1/Standard1:
 min = 4,  max = 32


CASSANDRA-CLI:
$> /Users/alexzarutin/.ccm/test-1.2.6/node1/bin/cassandra-cli -host localhost -port 9160
            
Connected to: "test-1.2.6" on localhost/9160
Welcome to Cassandra CLI version 1.2.6-SNAPSHOT

[default@unknown] show schema;

use Keyspace1;
create column family Standard1
  with column_type = 'Standard' 
  ....
  and min_compaction_threshold = 4
  and max_compaction_threshold = 32


Full repro steps are attached. 
I suggest to resolve this bug as "not repro on latest code". 

                
> 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
>            Assignee: Alex Zarutin
>            Priority: Minor
>         Attachments: CASSANDRA-3416.txt
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message