[
https://issues.apache.org/jira/browse/CASSANDRA-9035?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14610619#comment-14610619
]
Aleksey Yeschenko commented on CASSANDRA-9035:
----------------------------------------------
bq. It's done.
Nicely done. Committed to trunk as {{e89d54865ed9e69cb2b0081559936d1d2ee9b7c7}}
with some minor nits self-addressed:
- {{Config.hinted_handoff_enabled}} should've remained {{volatile}}
- {{YamlConfigurationLoader.CustomConstructor}} cleaned up a bit, and made to
conform code style
- removed redundant {{@Override}} annotations in {{EnableHintsForDC}} and
{{DisableHintsForDC}} ({{execute}} is {{abstract}}.
Plus, committed the deprecation note to cassandra-2.2 branch as
{{fbe96b3dfd2d73889c134e1c7006c197d4c3386d}}.
> Fix hinted_handoff_enabled yaml setting
> ---------------------------------------
>
> Key: CASSANDRA-9035
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9035
> Project: Cassandra
> Issue Type: Sub-task
> Reporter: Stefania
> Assignee: Stefania
> Priority: Minor
> Fix For: 3.0 beta 1
>
> Attachments: 9035-2.2.txt
>
>
> As discussed in CASSANDRA-6157, at the moment we have a single parameter
> {{hinted_handoff_enabled}} that can be either a boolean or a csv list of
> enabled data centers.
> We should have a boolean global {{hinted_handoff_enabled}} param plus a
> separate yaml list for the HH DC blacklist -
> {{hinted_handoff_disabled_datacenters}} to be checked when the global flag is
> on.
> Backward compatibility with the existing approach should be kept.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)