cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Zotov (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-4761) Async hints delivery
Date Thu, 11 Oct 2012 15:21:03 GMT


Alexey Zotov commented on CASSANDRA-4761:

I've attached file with discussed fixes. Also I've added some test for slice queries on expired

One more question, in 1.1 version there is the following bug:
When destination node has been down during hints delivery process, source node doesn't stop
the process. It tries to send hints until destination node won't be up again. Should I create
separate ticket or can simply attach patch to it?

> Async hints delivery
> --------------------
>                 Key: CASSANDRA-4761
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Alexey Zotov
>            Assignee: Alexey Zotov
>              Labels: hintedhandoff
>             Fix For: 1.2.0 beta 2
>         Attachments: cassandra-1.1-4761-async_hints.txt, cassandra-1.2-4761-async_hints.txt,
> Hints delivery to remote DC can take a long time (currently we have 70 ms for each hint).
In our estimates 700 MB of data (stored hints) will be transmitting to remote DC more than
one day (in our case), it's unacceptable for us. We suggest to enter hints delivery using
batch operations. 
> What do you think about it? Is there some facts that won't allow to implement that mechanism?
> I'll try to implement it if you approve and clarify right way.

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