Return-Path: X-Original-To: apmail-cassandra-commits-archive@www.apache.org Delivered-To: apmail-cassandra-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DE8FA11819 for ; Tue, 8 Apr 2014 19:21:19 +0000 (UTC) Received: (qmail 30399 invoked by uid 500); 8 Apr 2014 19:21:19 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 30365 invoked by uid 500); 8 Apr 2014 19:21:17 -0000 Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cassandra.apache.org Delivered-To: mailing list commits@cassandra.apache.org Received: (qmail 30331 invoked by uid 99); 8 Apr 2014 19:21:15 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Apr 2014 19:21:15 +0000 Date: Tue, 8 Apr 2014 19:21:14 +0000 (UTC) From: "Russ Hatch (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-6971) nodes not catching up to creation of new keyspace MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-6971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13963330#comment-13963330 ] Russ Hatch commented on CASSANDRA-6971: --------------------------------------- I ran the test 10 times with the patch (modified a bit) and the problem does not seem to be happening anymore. > nodes not catching up to creation of new keyspace > ------------------------------------------------- > > Key: CASSANDRA-6971 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6971 > Project: Cassandra > Issue Type: Bug > Reporter: Russ Hatch > Assignee: Brandon Williams > Attachments: 6971-debugging.txt, 6971.txt, debug1.log, debug2.log, debug3.log, node1.log, node1.log, node2.log, node2.log, node3.log, node3.log > > > The dtest suite is running a test which creates a 3 node cluster, then adds a keyspace and column family. For some reason the 3 nodes are not agreeing on the schema version. The problem is intermittent -- either the nodes all agree on schema quickly, or they seem to stay stuck in limbo. > The simplest way to reproduce is to run the dtest (simple_increment_test): > https://github.com/riptano/cassandra-dtest/blob/master/counter_tests.py > using nosetests: > {noformat} > nosetests -vs counter_tests.py:TestCounters.simple_increment_test > {noformat} > If the problem is reproduced nose will return this: > ProgrammingError: Bad Request: Keyspace 'ks' does not exist > I am not yet sure if the bug is reproducible outside of the dtest suite. -- This message was sent by Atlassian JIRA (v6.2#6252)