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

memtable_total_space_in_mb does not accept the value 0 in Cassandra 1.0

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Low
    • Resolution: Fixed
    • Fix Version/s: 1.0.0
    • Component/s: None
    • Labels:
      None
    • Severity:
      Low

      Description

      This affects 1.0 beta1.

      From the key explanation in cassandra.yaml it looks like it should accept the value "0"

      1. Total memory to use for memtables. Cassandra will flush the largest
      2. memtable when this much memory is used.
      3. If omitted, Cassandra will set it to 1/3 of the heap.
      4. If set to 0, only the old flush thresholds are used.
        memtable_total_space_in_mb: 0

      However in the code I could see the following:

      if (conf.memtable_total_space_in_mb <= 0)
      throw new ConfigurationException("memtable_total_space_in_mb must be positive");
      logger.info("Global memtable threshold is enabled at {}MB", conf.memtable_total_space_in_mb);

        Attachments

          Activity

            People

            • Assignee:
              jbellis Jonathan Ellis
              Reporter:
              thobbs Tyler Hobbs
              Authors:
              Jonathan Ellis
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: