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

Standardise config and JVM parameters

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Patch Available
    • Priority: Normal
    • Resolution: Unresolved
    • Fix Version/s: 4.0-alpha
    • Component/s: Local/Config
    • Labels:
      None

      Description

      We have a bunch of inconsistent names and config patterns in the codebase, both from the yams and JVM properties. It would be nice to standardise the naming (such as otc_ vs internode_) as well as the provision of values with units - while maintaining perpetual backwards compatibility with the old parameter names, of course.

      For temporal units, I would propose parsing strings with suffixes of:

      code
      u|micros(econds?)?
      ms|millis(econds?)?
      s(econds?)?
      m(inutes?)?
      h(ours?)?
      d(ays?)?
      mo(nths?)?
      code

      For rate units, I would propose parsing any of the standard B/s, KiB/s, MiB/s, GiB/s, TiB/s.
      Perhaps for avoiding ambiguity we could not accept bauds bs, Mbps or powers of 1000 such as KB/s, given these are regularly used for either their old or new definition e.g. KiB/s, or we could support them and simply log the value in bytes/s.

        Attachments

        1. CASSANDRA-15234-3-DTests-JAVA8.txt
          8 kB
          Ekaterina Dimitrova

          Issue Links

            Activity

              People

              • Assignee:
                e.dimitrova Ekaterina Dimitrova
                Reporter:
                benedict Benedict Elliott Smith
                Authors:
                Ekaterina Dimitrova
                Reviewers:
                Benjamin Lerer, Michael Semb Wever
              • Votes:
                0 Vote for this issue
                Watchers:
                23 Start watching this issue

                Dates

                • Created:
                  Updated: