Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Fri, 22 Apr 2011 16:04:05 +0000 (UTC)
From: "Tyler Hobbs (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: 
 <475286894.76599.1303488245785.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <21470429.74976.1303426625803.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (CASSANDRA-2536) Schema disagreements when using
 connections to multiple hosts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Tyler Hobbs commented on CASSANDRA-2536:
----------------------------------------

Actually, I can also reproduce this with a two node 0.7.4 cluster.  I'm pretty sure that this does not happen with 0.7.3, but I'll go ahead and verify that.

> Schema disagreements when using connections to multiple hosts
> -------------------------------------------------------------
>
>                 Key: CASSANDRA-2536
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-2536
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 0.8 beta 1
>         Environment: Two node 0.8-beta1 cluster with one seed and JNA.
>            Reporter: Tyler Hobbs
>            Assignee: Gary Dusbabek
>         Attachments: schema_disagree.py
>
>
> If you have two thrift connections open to different nodes and you create a KS using the first, then a CF in that KS using the second, you wind up with a schema disagreement even if you wait/sleep after creating the KS.
> The attached script reproduces the issue using pycassa (1.0.6 should work fine, although it has the 0.7 thrift-gen code).  It's also reproducible by hand with two cassandra-cli sessions.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira