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 59E5617D03 for ; Fri, 17 Apr 2015 19:56:00 +0000 (UTC) Received: (qmail 18223 invoked by uid 500); 17 Apr 2015 19:56:00 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 18173 invoked by uid 500); 17 Apr 2015 19:56:00 -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 18161 invoked by uid 99); 17 Apr 2015 19:56:00 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Apr 2015 19:56:00 +0000 Date: Fri, 17 Apr 2015 19:56:00 +0000 (UTC) From: "Brandon Williams (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CASSANDRA-8072) Exception during startup: Unable to gossip with any seeds MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/CASSANDRA-8072?page=3Dcom.atlas= sian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D= 14500554#comment-14500554 ]=20 Brandon Williams commented on CASSANDRA-8072: --------------------------------------------- The reason this only manifests with shadow gossip is because shadow is the = only time we send precisely one round, under normal gossip conditions we fi= re once per second, but probably lose the first message as well. > Exception during startup: Unable to gossip with any seeds > --------------------------------------------------------- > > Key: CASSANDRA-8072 > URL: https://issues.apache.org/jira/browse/CASSANDRA-8072 > Project: Cassandra > Issue Type: Bug > Reporter: Ryan Springer > Assignee: Brandon Williams > Fix For: 2.0.15, 2.1.5 > > Attachments: cas-dev-dt-01-uw1-cassandra-seed01_logs.tar.bz2, cas= -dev-dt-01-uw1-cassandra-seed02_logs.tar.bz2, cas-dev-dt-01-uw1-cassandra02= _logs.tar.bz2, casandra-system-log-with-assert-patch.log, trace_logs.tar.bz= 2 > > > When Opscenter 4.1.4 or 5.0.1 tries to provision a 2-node DSC 2.0.10 clus= ter in either ec2 or locally, an error occurs sometimes with one of the nod= es refusing to start C*. The error in the /var/log/cassandra/system.log is= : > ERROR [main] 2014-10-06 15:54:52,292 CassandraDaemon.java (line 513) Exce= ption encountered during startup > java.lang.RuntimeException: Unable to gossip with any seeds > at org.apache.cassandra.gms.Gossiper.doShadowRound(Gossiper.java:= 1200) > at org.apache.cassandra.service.StorageService.checkForEndpointCo= llision(StorageService.java:444) > at org.apache.cassandra.service.StorageService.prepareToJoin(Stor= ageService.java:655) > at org.apache.cassandra.service.StorageService.initServer(Storage= Service.java:609) > at org.apache.cassandra.service.StorageService.initServer(Storage= Service.java:502) > at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDa= emon.java:378) > at org.apache.cassandra.service.CassandraDaemon.activate(Cassandr= aDaemon.java:496) > at org.apache.cassandra.service.CassandraDaemon.main(CassandraDae= mon.java:585) > INFO [StorageServiceShutdownHook] 2014-10-06 15:54:52,326 Gossiper.java = (line 1279) Announcing shutdown > INFO [StorageServiceShutdownHook] 2014-10-06 15:54:54,326 MessagingServi= ce.java (line 701) Waiting for messaging service to quiesce > INFO [ACCEPT-localhost/127.0.0.1] 2014-10-06 15:54:54,327 MessagingServi= ce.java (line 941) MessagingService has terminated the accept() thread > This errors does not always occur when provisioning a 2-node cluster, but= probably around half of the time on only one of the nodes. I haven't been= able to reproduce this error with DSC 2.0.9, and there have been no code o= r definition file changes in Opscenter. > I can reproduce locally with the above steps.=E2=80=82 I'm happy to test = any proposed fixes since I'm the only person able to reproduce reliably so = far. -- This message was sent by Atlassian JIRA (v6.3.4#6332)