[jira] [Assigned] (CASSANDRA-2536) Schema disagreements when using connections to multiple hosts
[ https://issues.apache.org/jira/browse/CASSANDRA-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tyler Hobbs reassigned CASSANDRA-2536: -- Assignee: Tyler Hobbs (was: Gary Dusbabek) > 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: Tyler Hobbs > 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
[jira] [Assigned] (CASSANDRA-2536) Schema disagreements when using connections to multiple hosts
[ https://issues.apache.org/jira/browse/CASSANDRA-2536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jonathan Ellis reassigned CASSANDRA-2536: - Assignee: Gary Dusbabek And this is fine in 0.7? > 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
