cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Tryuber (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4768) Add separate max_hint_window_in_ms option for remote data centers
Date Mon, 08 Oct 2012 18:14:04 GMT


Sergey Tryuber commented on CASSANDRA-4768:

Brandon, you're right. But we're talking about the period of time we can rely on hinted handoff.
If there is only one configuration option, we must set it up considering the worst case: lack
of cross datacenter connectivity. Because in that case a lot of hints will be saved. For local
DC (one-two node failures in most of the cases) not as many data will be saved as hints. So
larger window size can be configured (and admins can sleep well at nights or maintain servers
without being in a hurry). 

I understand that Cassandra is well known as "easy to set up" (despite of HBase). So may be
we can add this option as a "hidden" with only one default value in cassandra.yaml for both
windows (the same approach is used by Hadoop, Hive and HBase). 
> Add separate max_hint_window_in_ms option for remote data centers
> -----------------------------------------------------------------
>                 Key: CASSANDRA-4768
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1.2
>            Reporter: Alexey Zotov
>            Assignee: Alexey Zotov
>            Priority: Minor
>              Labels: configuration, hintedhandoff
>             Fix For: 1.1.6, 1.2.0
>         Attachments: cassandra-1.1-4768-remote_hint_window.txt, cassandra-1.2-4768-remote_hint_window.txt
> It would be nice to have possibility to configure hint window size for remote dc separately.
It will allow to prevent accumulating of big amount of data for remote dc and long hints delivery
as the result of it.
> I suggest to add max_hint_window_for_remote_dc_in_ms option. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message