[
https://issues.apache.org/jira/browse/CASSANDRA-15234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17091157#comment-17091157
]
Ekaterina Dimitrova edited comment on CASSANDRA-15234 at 4/24/20, 4:14 AM:
---------------------------------------------------------------------------
Latest update:
Part1
- format issues fixed
- The isOldYAML logger info changed to warn, and it lists also the old
properties used
- The format of yaml props is noun_verb. native_transport props adjusted to
follow this. Max sent to the back as in native_transport_threads_max.
- MAP_OLD_TO_NEW_PARAMETERS is not static anymore(so it is freed memory
after startup)
Part2 - will be completed in the suggested way probably tomorrow (working
asynchronously)
Part3 - anyone any thoughts whether it should be 1 class or maybe divided into
3 classes as suggested by [~dcapwell]?
was (Author: e.dimitrova):
Latest update:
Part1
- format issues fixed
- The isOldYAML logger info changed to warn, and it lists also the old
properties used
- The format of yaml props is noun_verb? native_transport props adjusted to
follow this. Max sent to the back as in native_transport_threads_max.
- MAP_OLD_TO_NEW_PARAMETERS is not static (so it is freed memory after
startup)
Part2 - will be completed in the suggested way probably tomorrow (working
asynchronously)
Part3 - anyone any thoughts whether it should be 1 class or maybe divided into
3 classes as suggested by [~dcapwell]?
> 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: 4.0, 4.0-beta
>
>
> 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]
