cassandra-commits mailing list archives

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

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

Sylvain Lebresne commented on CASSANDRA-3554:
---------------------------------------------

Couldn't B handles this? When it drops writes from A, it could record it. Then B could have
a scheduled tasks that looks for locally dropped writes and decide if it's ok to get hints
based on the mutation stage queue. It could then request the hint delivery from A.
                
> 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