[
https://issues.apache.org/jira/browse/CASSANDRA-9691?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610031#comment-14610031
]
Aleksey Yeschenko commented on CASSANDRA-9691:
----------------------------------------------
There is also JMX and metrics, where we can't do that, but should standardize
on a single lowest unit for each dimension instead.
Plus some {{CREATE TABLE}} params. All can/should be handled in separate JIRAs
ofc.
> Liberate cassandra.yaml parameter names from their units
> --------------------------------------------------------
>
> Key: CASSANDRA-9691
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9691
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Benedict
> Assignee: Benedict
> Priority: Minor
> Fix For: 3.x
>
>
> The arbitrary units have bugged me for too long.
> I would like to see, instead of {{trickle_fsync_interval_in_kb=1024}}
> {{trickle_fsync_interval=1MiB}}, and instead of {{max_hint_window_in_ms = 3 *
> 3600 * 1000}}, {{max_hint_window=3h}}
> We aren't currently even consistent, with {{counter_cache_save_period}} not
> specifying its units, and {{stream_throughput_outbound_megabits_per_sec=200}}
> is tremendously ugly (vs {{inter_dc_stream_throughput_outbound=25MiB/s}} or
> {{inter_dc_stream_throughput_outbound=200MBit/s}})
> This is really trivial, and would make our config file look a lot less ugly.
> Of course, we'll have to support both in parallel for a period.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
