cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeff Jirsa (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13976) introduce max_hint_window_in_min, deprecate max_hint_window_in_ms
Date Fri, 01 Dec 2017 01:03:00 GMT


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:
>             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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message