cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (Created) (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-3577) TimeoutException When using QuorumEach or ALL consistency on Multi-DC
Date Tue, 06 Dec 2011 03:31:39 GMT
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
             Fix For: 0.8.9


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