You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2012/10/04 17:45:47 UTC

[jira] [Commented] (CASSANDRA-4761) Batch hints delivery

    [ https://issues.apache.org/jira/browse/CASSANDRA-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13469460#comment-13469460 ] 

Jonathan Ellis commented on CASSANDRA-4761:
-------------------------------------------

I don't think they are very similar.  4047 is about "how can I hint an entire sstable," and this is about "how can I optimize hint delivery over the WAN."

Personally I don't think you'd be well-served by writing out sstables locally for hints and streaming them over.  Easier and more effective to make hint delivery asynchronous -- instead of waiting for each hint to be acked before sending another, send hints continuously (until throttled) and create callbacks to delete successfully delivered ones.
                
> Batch hints delivery
> --------------------
>
>                 Key: CASSANDRA-4761
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4761
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 1.1.2
>            Reporter: Alexey Zotov
>            Assignee: Alexey Zotov
>              Labels: hintedhandoff
>
> 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: http://www.atlassian.com/software/jira