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 692AC184EF for ; Mon, 22 Feb 2016 15:54:51 +0000 (UTC) Received: (qmail 62995 invoked by uid 500); 22 Feb 2016 15:40:21 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 62974 invoked by uid 500); 22 Feb 2016 15:40:21 -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 62956 invoked by uid 99); 22 Feb 2016 15:40:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 22 Feb 2016 15:40:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 297922C1F68 for ; Mon, 22 Feb 2016 15:40:18 +0000 (UTC) Date: Mon, 22 Feb 2016 15:40:18 +0000 (UTC) From: "Michael Shuler (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-11197) upgrade bootstrap tests flap when migration tasks fail 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-11197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15157151#comment-15157151 ] Michael Shuler commented on CASSANDRA-11197: -------------------------------------------- node5.log ends at: {noformat} INFO [GossipTasks:1] 2016-02-20 11:58:52,963 Gossiper.java:407 - removed /127.0.0.3 from seeds, updated seeds list = [/127.0.0.1, /127.0.0.2] INFO [StreamReceiveTask:1] 2016-02-20 11:58:52,986 StreamResultFuture.java:182 - [Stream #4f8f0700-d7c9-11e5-aa1b-6bb09ae6f4ab] Session with /127.0.0.1 is complete INFO [StreamReceiveTask:1] 2016-02-20 11:58:52,991 StreamResultFuture.java:214 - [Stream #4f8f0700-d7c9-11e5-aa1b-6bb09ae6f4ab] All sessions completed INFO [StreamReceiveTask:1] 2016-02-20 11:58:52,992 StorageService.java:1278 - Bootstrap completed! for the tokens [-1046036964622941990, -1400890082314916278, -1616734794216760014, -1730354115286784558, -231240216319146652, -2886293344383011530, -3154076435162348814, -393404753600801543, -4557709796699750607, -4697610942640796701, -4761422343701626080, -5648668112035479498, -5816636489400216585, -6065580273470025023, -6375421974841622668, -6563358416162091008, -7556456891324157361, -8945667139064518906, 1586138857784476133, 1592015304628531453, 211888626044588620, 2416115270185069432, 3574440533325868089, 3754114748069577639, 4310690373752819510, 4492447081526739284, 4894096440905697039, 5907859292516510425, 6530253410888883793, 7289629350545575444, 7870640173315649762, 9174862021047208140] INFO [main] 2016-02-20 11:58:53,019 StorageService.java:1983 - Node /127.0.0.5 state jump to NORMAL INFO [main] 2016-02-20 11:58:53,027 CassandraDaemon.java:638 - Waiting for gossip to settle before accepting client requests... {noformat} ..and nothing after that, so the test was failed out. Your thought in your next comment that 1 second is probably too low may be spot on. > upgrade bootstrap tests flap when migration tasks fail > ------------------------------------------------------ > > Key: CASSANDRA-11197 > URL: https://issues.apache.org/jira/browse/CASSANDRA-11197 > Project: Cassandra > Issue Type: Bug > Reporter: Jim Witschey > Assignee: DS Test Eng > Labels: dtest > > I've seen these tests flap: > {code} > upgrade_tests/upgrade_through_versions_test.py:ProtoV4Upgrade_3_1_UpTo_3_2_HEAD.bootstrap_test > upgrade_tests/upgrade_through_versions_test.py:ProtoV4Upgrade_3_3_UpTo_Trunk_HEAD.bootstrap_test > upgrade_tests/upgrade_through_versions_test.py:ProtoV3Upgrade_3_0_UpTo_3_1_HEAD.bootstrap_multidc_test > upgrade_tests/upgrade_through_versions_test.py:ProtoV3Upgrade_3_2_UpTo_3_3_HEAD.bootstrap_multidc_test > upgrade_tests/upgrade_through_versions_test.py:ProtoV3Upgrade_3_3_UpTo_Trunk_HEAD.bootstrap_multidc_test > upgrade_tests/upgrade_through_versions_test.py:ProtoV4Upgrade_3_3_UpTo_Trunk_HEAD.bootstrap_multidc_test > {code} > There may be more upgrade paths that flap, I'm not sure. All the failures I've seen look like this: > {code} > Unexpected error in node5 node log: ['ERROR [main] 2016-02-18 20:05:13,012 MigrationManager.java:164 - Migration task failed to complete\nERROR [main] 2016-02-18 20:05:14,012 MigrationManager.java:164 - Migration task failed to complete'] > {code} > [~rhatch] Do these look familiar at all? -- This message was sent by Atlassian JIRA (v6.3.4#6332)