cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-4761) Async hints delivery
Date Wed, 10 Oct 2012 18:25:07 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jonathan Ellis updated CASSANDRA-4761:
--------------------------------------

    Affects Version/s:     (was: 1.1.2)
        Fix Version/s: 1.2.0 beta 2
              Summary: Async hints delivery  (was: Batch hints delivery)

Thanks for the patch.  At a high level things look reasonable.  Some feedback:

- patch needs to be against trunk
- you're not going to gain much from adding multiple threads to RowMutation delivery, since
it has to go over the same MessagingService thread anyway.  We do want to allow multiple threads
to allow parallelism across multiple destinations, but trunk already supports this.
                
> Async hints delivery
> --------------------
>
>                 Key: CASSANDRA-4761
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4761
>             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, notices.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: http://www.atlassian.com/software/jira

Mime
View raw message