cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefania (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9035) Fix hinted_handoff_enabled yaml setting
Date Mon, 22 Jun 2015 04:04:01 GMT


Stefania commented on CASSANDRA-9035:

[~iamaleksey] I started looking into this today, sorry about the delay.

CASSANDRA-6157 extended _nodetool enablehandoff_ to receive an optional list of data centers
in order to enable hinted handoff only for these data centers. Do we need to keep compatibility
with this? If so, it's a bit problematic to only store a list of disabled datacenters. A new
data center would have hinted handoff enabled even if it is not in the initial list specified
with this command. What do you think?


> Fix hinted_handoff_enabled yaml setting
> ---------------------------------------
>                 Key: CASSANDRA-9035
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Stefania
>            Assignee: Stefania
>            Priority: Minor
>             Fix For: 3.x
> 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

View raw message