You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Benedict (JIRA)" <ji...@apache.org> on 2019/07/17 07:33:00 UTC

[jira] [Created] (CASSANDRA-15234) Standardise config and JVM parameters

Benedict created CASSANDRA-15234:
------------------------------------

             Summary: Standardise config and JVM parameters
                 Key: CASSANDRA-15234
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-15234
             Project: Cassandra
          Issue Type: Bug
            Reporter: Benedict


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?)?
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.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org