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-3577) TimeoutException When using QuorumEach or ALL consistency on Multi-DC
Date Tue, 06 Dec 2011 04:25:39 GMT

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

Jonathan Ellis commented on CASSANDRA-3577:
-------------------------------------------

You're right, we switched to using unique message IDs per target in CASSANDRA-2058 so that
we can track timeouts for the dynamic snitch, so my patch won't work.

I agree that pre-generating extra IDs on the coordinator is the easiest fix, and also that
we should just disable this behavior in 0.8 (which was the case until CASSANDRA-3472 anyway).
                
> TimeoutException When using QuorumEach or ALL consistency on Multi-DC
> ---------------------------------------------------------------------
>
>                 Key: CASSANDRA-3577
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3577
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.8
>         Environment: JVM
>            Reporter: Vijay
>            Assignee: Vijay
>             Fix For: 0.8.9
>
>         Attachments: 3577.txt
>
>
> Currently we have 
> 1) StorageProxy.sendMessages() sending messages to the first node in the other DC...
 
> 2) A node in the other DC will remove the ForwardHeader and sendRR (Adding a MessageID
to the Queue).
> 3) The receiving node receives the mutation, updates and sends the response to the Original
Co-ordinator.
> 4) Co-Ordinator now checks for the MessageID (which it never had)
> All the Quorum_Each updates fail in the co-ordinator, this issue started showing up after
CASSANDRA-3472 the code was introduced in CASSANDRA-2138 .
> Simple Fix is to remove the optimization in 0.8 and fix it in 1.x because it seems to
me like it needs a change to the Message service version.
> Possible Solution: We might want send the message ID's to be used by the all the nodes
in other DC (Which is currently generated by the node which receives the Forward request see:
(2) ).

--
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