[
https://issues.apache.org/jira/browse/CASSANDRA-9076?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14388679#comment-14388679
]
Jeff Jirsa commented on CASSANDRA-9076:
---------------------------------------
The change itself is trivial and should be safe. At least 3.0 and 2.1. The
issue was mentioned when it bit a 2.0 user.
I know 2.0 is fairly late in the game at this point, but this is also a pretty
non-invasive change - I'd personally like to see it in 2.0, but I'll live
either way, since there's an easy cassandra.yaml workaround for getting 3hrs
instead of 1hr. Up to Aleksey.
> Consistency: make default max_hint_window_in_ms actually 3 hours
> ----------------------------------------------------------------
>
> Key: CASSANDRA-9076
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9076
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Jeff Jirsa
> Assignee: Jeff Jirsa
> Priority: Trivial
> Fix For: 3.0, 2.1.4
>
> Attachments: max_hint_window.diff
>
>
> From IRC/#cassandra:
> CASSANDRA-4632 changed max_hint_window_in_ms from 1 hour to 3 hours, however,
> it only changed the default in cassandra.yaml - it left the actual default in
> Config.java at 1 hour.
> This issue is to update Config.java for consistency, in case users comment
> out the actual entry in cassandra.yaml and revert to the "real" default of 1
> hour.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
