[ https://issues.apache.org/jira/browse/CASSANDRA-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13033159#comment-13033159 ]
Stu Hood commented on CASSANDRA-2034: ------------------------------------- bq. Better would be to add a hook to messagingservice callback expiration, and fire hint recording from there bq. So I think what we want to do, with this option on, is to attempt the hint write but if we can't do it in a reasonable time... +1. An expiration handler on the messaging service queue, and throttled local hint writing should work very well. > Make Read Repair unnecessary when Hinted Handoff is enabled > ----------------------------------------------------------- > > Key: CASSANDRA-2034 > URL: https://issues.apache.org/jira/browse/CASSANDRA-2034 > Project: Cassandra > Issue Type: Improvement > Components: Core > Reporter: Jonathan Ellis > Assignee: Jonathan Ellis > Fix For: 1.0 > > Original Estimate: 8h > Remaining Estimate: 8h > > Currently, HH is purely an optimization -- if a machine goes down, enabling > HH means RR/AES will have less work to do, but you can't disable RR entirely > in most situations since HH doesn't kick in until the FailureDetector does. > Let's add a scheduled task to the mutate path, such that we return to the > client normally after ConsistencyLevel is achieved, but after RpcTimeout we > check the responseHandler write acks and write local hints for any missing > targets. > This would making disabling RR when HH is enabled a much more reasonable > option, which has a huge impact on read throughput. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira