Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-3416

nodetool and show schema give different value for compact threshold

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Low
    • Resolution: Cannot Reproduce
    • None
    • Tool/nodetool
    • None
    • ALL

    • Low

    Description

      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

      >

      >

      Attachments

        1. CASSANDRA-3416.txt
          6 kB
          Alex Zarutin

        Activity

          People

            alexzar Alex Zarutin
            leeworld88 mike li
            Alex Zarutin
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: