Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2495C200B67 for ; Mon, 1 Aug 2016 16:35:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 23408160A66; Mon, 1 Aug 2016 14:35:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 73D6E160A6C for ; Mon, 1 Aug 2016 16:35:21 +0200 (CEST) Received: (qmail 54022 invoked by uid 500); 1 Aug 2016 14:35:20 -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 53984 invoked by uid 99); 1 Aug 2016 14:35:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Aug 2016 14:35:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 7B6A32C0059 for ; Mon, 1 Aug 2016 14:35:20 +0000 (UTC) Date: Mon, 1 Aug 2016 14:35:20 +0000 (UTC) From: "Paulo Motta (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (CASSANDRA-11687) dtest failure in rebuild_test.TestRebuild.simple_rebuild_test MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Mon, 01 Aug 2016 14:35:22 -0000 [ https://issues.apache.org/jira/browse/CASSANDRA-11687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Paulo Motta updated CASSANDRA-11687: ------------------------------------ Status: Open (was: Patch Available) What is probably happening here is that the second rebuild is completing before the first, so the first rebuild fails while the second succeeds, but we expect the second rebuild to fail. I think we should modify the test to insert more data (10k or 100k keys) with stress and set {{streaming_throughput_mb_per_sec=1}} similar to bootstrap and replace_address tests, trigger the first rebuild and {{watch_log_for("rebuilding from")}}, and then trigger the second rebuild and expect it to fail to make this more deterministic. > dtest failure in rebuild_test.TestRebuild.simple_rebuild_test > ------------------------------------------------------------- > > Key: CASSANDRA-11687 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11687 > Project: Cassandra > Issue Type: Bug > Reporter: Russ Hatch > Assignee: Yuki Morishita > Labels: dtest > > single failure on most recent run (3.0 no-vnode) > {noformat} > concurrent rebuild should not be allowed, but one rebuild command should have succeeded. > {noformat} > http://cassci.datastax.com/job/cassandra-3.0_novnode_dtest/217/testReport/rebuild_test/TestRebuild/simple_rebuild_test > Failed on CassCI build cassandra-3.0_novnode_dtest #217 -- This message was sent by Atlassian JIRA (v6.3.4#6332)