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 EE3D211012 for ; Sat, 7 Jun 2014 01:13:01 +0000 (UTC) Received: (qmail 50806 invoked by uid 500); 7 Jun 2014 01:13:01 -0000 Delivered-To: apmail-cassandra-commits-archive@cassandra.apache.org Received: (qmail 50773 invoked by uid 500); 7 Jun 2014 01:13:01 -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 50762 invoked by uid 99); 7 Jun 2014 01:13:01 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 07 Jun 2014 01:13:01 +0000 Date: Sat, 7 Jun 2014 01:13:01 +0000 (UTC) From: "Jackson Chung (JIRA)" To: commits@cassandra.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CASSANDRA-7363) PropertyFileSnitch should allow name address that does not yet exist MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Jackson Chung created CASSANDRA-7363: ---------------------------------------- Summary: PropertyFileSnitch should allow name address that does not yet exist Key: CASSANDRA-7363 URL: https://issues.apache.org/jira/browse/CASSANDRA-7363 Project: Cassandra Issue Type: Bug Reporter: Jackson Chung when starting a new node with PropertyFileSnitch with cassandra-topology.properties contains an unknown host, it fails with: {noformat} ERROR [main] 2014-06-06 17:48:38,233 DatabaseDescriptor.java (line 116) Fatal configuration error org.apache.cassandra.exceptions.ConfigurationException: Error instantiating snitch class 'org.apache.cassandra.locator.PropertyFileSnitch'. at org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:503) at org.apache.cassandra.config.DatabaseDescriptor.createEndpointSnitch(DatabaseDescriptor.java:506) at org.apache.cassandra.config.DatabaseDescriptor.applyConfig(DatabaseDescriptor.java:341) at org.apache.cassandra.config.DatabaseDescriptor.(DatabaseDescriptor.java:111) at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:155) at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:480) at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:569) Caused by: org.apache.cassandra.exceptions.ConfigurationException: Unknown host cassandra11-staging.amz.relateiq.com at org.apache.cassandra.locator.PropertyFileSnitch.reloadConfiguration(PropertyFileSnitch.java:174) at org.apache.cassandra.locator.PropertyFileSnitch.(PropertyFileSnitch.java:60) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:408) at java.lang.Class.newInstance(Class.java:433) at org.apache.cassandra.utils.FBUtilities.construct(FBUtilities.java:488) ... 6 more Caused by: java.net.UnknownHostException: cassandra11-staging.amz.relateiq.com: unknown error at java.net.Inet4AddressImpl.lookupAllHostAddr(Native Method) at java.net.InetAddress$2.lookupAllHostAddr(InetAddress.java:907) at java.net.InetAddress.getAddressesFromNameService(InetAddress.java:1302) at java.net.InetAddress.getAllByName0(InetAddress.java:1255) at java.net.InetAddress.getAllByName(InetAddress.java:1171) at java.net.InetAddress.getAllByName(InetAddress.java:1105) at java.net.InetAddress.getByName(InetAddress.java:1055) at org.apache.cassandra.locator.PropertyFileSnitch.reloadConfiguration(PropertyFileSnitch.java:170) ... 13 more {noformat} The real impact here is we are trying to launch a number of new nodes (via chef) with pre-configured hostname (and among other variables). The additional hostname (but not yet alive) made no impact to the existing nodes, which is good (looks like we only catch the ConfigurationException in the watcher thread, but not on the initial start); but it causes new node fail to start. (Pretty sure if we restart an existing one, it will fail too). -- This message was sent by Atlassian JIRA (v6.2#6252)