cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergio Bossa (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-5692) Race condition in detecting version on a mixed 1.1/1.2 cluster
Date Sun, 23 Jun 2013 12:59:19 GMT
Sergio Bossa created CASSANDRA-5692:

             Summary: Race condition in detecting version on a mixed 1.1/1.2 cluster
                 Key: CASSANDRA-5692
             Project: Cassandra
          Issue Type: Bug
    Affects Versions: 1.2.5, 1.1.9
            Reporter: Sergio Bossa

On a mixed 1.1 / 1.2 cluster, starting 1.2 nodes fires sometimes a race condition in version
detection, where the 1.2 node wrongly detects version 6 for a 1.1 node.

It works as follows:
1) The just started 1.2 node quickly opens an OutboundTcpConnection toward a 1.1 node before
receiving any messages from the latter.
2) Given the version is correctly detected only when the first message is received, the version
is momentarily set at 6.
3) This opens an OutboundTcpConnection from 1.2 to 1.1 at version 6, which gets stuck in the
connect() method.

Later, the version is correctly fixed, but all outbound connections from 1.2 to 1.1 are stuck
at this point.

Evidence from 1.2 logs:
TRACE 13:48:31,133 Assuming current protocol version for /
DEBUG 13:48:37,837 Setting version 5 for /

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message