[
https://issues.apache.org/jira/browse/CASSANDRA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13162824#comment-13162824
]
T Jake Luciani commented on CASSANDRA-3554:
-------------------------------------------
The other problem is even if we fix the replay issue it's still terribly slow
due to excessive throttling
I like the idea of changing from a push to pull mode for hint delivery. Similar
to how mysql replication is client pull. Clients know how swamped they are and
can throttle their own delivery.
> Hints are not replayed unless node was marked down
> --------------------------------------------------
>
> Key: CASSANDRA-3554
> URL: https://issues.apache.org/jira/browse/CASSANDRA-3554
> Project: Cassandra
> Issue Type: Bug
> Reporter: Jonathan Ellis
>
> If B drops a write from A because it is overwhelmed (but not dead), A will
> hint the write. But it will never get notified that B is back up (since it
> was never down), so it will never attempt hint delivery.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
