[
https://issues.apache.org/jira/browse/CASSANDRA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13164481#comment-13164481
]
Edward Capriolo commented on CASSANDRA-3554:
--------------------------------------------
How expensive is the process of "1) Wake Up. 2)Check for hints. 3) try to
deliver them." As for parts 1 & 2 I would think we can do this more often then
hourly, maybe a background thread that sleeps for N seconds and attempts again.
{quote}
The other problem is even if we fix the replay issue it's still terribly slow
due to excessive throttling{quote} Side note. This throttle can not currently
be adjusted at runtime. This should be JMX able. The default may be too low.
Historically the problem was the hint sending node got hammered. In my mind the
throttle was protecting that system.
> 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
