[
https://issues.apache.org/jira/browse/CASSANDRA-15234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383461#comment-17383461
]
Ekaterina Dimitrova commented on CASSANDRA-15234:
-------------------------------------------------
Thank you [~benedict] and apologize for the late response. There was a lot of
multitasking lately.
{quote}it would be good to get some initial feedback on this approach to
grouping of config options, as optimising the groups is a laborious job that
there's no point pursuing if it's otherwise unwelcome.
{quote}
Absolutely agree with you. I personally have only that question for feedback,
whether they would prefer the sections or the nested version you suggested.
[~maedhroz], [~mck], [~paulo], [~blerer], [~dcapwell], [[email protected]]
(maybe [~stefan.miklosovic] as I know he was also interested into this work at
some point) - do you have anything to add here as concerns/comment before we
bring it to the user list?
Also, should it come from a PMC? Survey or just a discussion mail thread? I am
not familiar of any similar discussions before so I am not sure what would be
the right approach, I am open for suggestions/advice anyone might have. Thank
you.
> Standardise config and JVM parameters
> -------------------------------------
>
> Key: CASSANDRA-15234
> URL: https://issues.apache.org/jira/browse/CASSANDRA-15234
> Project: Cassandra
> Issue Type: Bug
> Components: Local/Config
> Reporter: Benedict Elliott Smith
> Assignee: Ekaterina Dimitrova
> Priority: Normal
> Fix For: 5.x
>
> Attachments: CASSANDRA-15234-3-DTests-JAVA8.txt
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
