cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Ellis (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-3554) Hints are not replayed unless node was marked down
Date Fri, 02 Dec 2011 05:49:40 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13161436#comment-13161436
] 

Jonathan Ellis commented on CASSANDRA-3554:
-------------------------------------------

Unclear how we should tell when it's a good idea to re-attempt delivery in this scenario.

Possibly the best solution is to just make FD smarter and mark nodes as "effectively down"
in this situation.  A "local" FD as in CASSANDRA-3533 could address this.
                
> 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

        

Mime
View raw message