cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vijay (Updated) (JIRA)" <>
Subject [jira] [Updated] (CASSANDRA-3577) TimeoutException When using QuorumEach or ALL consistency on Multi-DC
Date Wed, 07 Dec 2011 08:20:39 GMT


Vijay updated CASSANDRA-3577:

    Attachment: 0001-removing-mutation-MultiDC-optimization.patch

Testing took some additional time, This patch is on 1.1 with an updated MessagingService.version
to handle both older version and new version mutations.
> TimeoutException When using QuorumEach or ALL consistency on Multi-DC
> ---------------------------------------------------------------------
>                 Key: CASSANDRA-3577
>                 URL:
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8.8
>         Environment: JVM
>            Reporter: Vijay
>            Assignee: Vijay
>             Fix For: 0.8.9
>         Attachments: 0001-Mutation-Optimization-for-MultiDC.patch, 0001-removing-mutation-MultiDC-optimization.patch,
> 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
> 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:!default.jspa
For more information on JIRA, see:


View raw message