[
https://issues.apache.org/jira/browse/CASSANDRA-13976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273758#comment-16273758
]
Jeff Jirsa commented on CASSANDRA-13976:
----------------------------------------
We have 25 other config options that take millis. Why are we changing one, when
it's one that's rarely tuned anyway? There are plenty others (auth permission
validity) that is also almost certainly never set in milliseconds that you
haven't suggested changing. How do you propose we keep consistency there?
Is this really something where the ease of setting it once is going to outweigh
the config churn for the typical user?
> introduce max_hint_window_in_min, deprecate max_hint_window_in_ms
> -----------------------------------------------------------------
>
> Key: CASSANDRA-13976
> URL: https://issues.apache.org/jira/browse/CASSANDRA-13976
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jon Haddad
> Assignee: Kirk True
> Priority: Minor
> Labels: lhf
> Fix For: 4.0
>
>
> Milliseconds is unnecessarily precise. At most, minutes would be used.
> Config in 4.0 should default to a minute granularity, but if the
> max_hint_window_in_min isn't set should fall back on max_hint_window_in_ms
> and emit a warning.
> max_hint_window_in_min: 180 # new default, still at 3 hours.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
