[
https://issues.apache.org/jira/browse/CASSANDRA-4761?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13474507#comment-13474507
]
Alexey Zotov commented on CASSANDRA-4761:
-----------------------------------------
It's needed to handle situation when some hints were not delivered because of
timeouts. I see only one way to do that - it's to make a new slice query and if
it won't find anything - all hints have been successfully delivered.
So when the first time we get "paging finished" condition (we've simply sent
all hints without any checking) the startColumn is not equal to EMPTY. And then
we'are trying to do the same query from the first column. If we find anything
we'll continue hints delivery because found hints have been timed out and not
deleted. If we don't find anything we'll exit because startColumn is equal to
EMPTY.
Do you have another thoughts about how to handle timeouts?
> 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,
> cassandra-1.2-4761-async_hints.txt, cassandra-1.2-4761-async_hints-v2.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
