cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jackson Chung (JIRA)" <>
Subject [jira] [Created] (CASSANDRA-7363) PropertyFileSnitch should allow name address that does not yet exist
Date Sat, 07 Jun 2014 01:13:01 GMT
Jackson Chung created CASSANDRA-7363:

             Summary: PropertyFileSnitch should allow name address that does not yet exist
                 Key: CASSANDRA-7363
             Project: Cassandra
          Issue Type: Bug
            Reporter: Jackson Chung

when starting a new node with PropertyFileSnitch with contains
an unknown host, it fails with:

ERROR [main] 2014-06-06 17:48:38,233 (line 116) Fatal configuration
org.apache.cassandra.exceptions.ConfigurationException: Error instantiating snitch class 'org.apache.cassandra.locator.PropertyFileSnitch'.
        at org.apache.cassandra.utils.FBUtilities.construct(
        at org.apache.cassandra.config.DatabaseDescriptor.createEndpointSnitch(
        at org.apache.cassandra.config.DatabaseDescriptor.applyConfig(
        at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(
        at org.apache.cassandra.service.CassandraDaemon.setup(
        at org.apache.cassandra.service.CassandraDaemon.activate(
        at org.apache.cassandra.service.CassandraDaemon.main(
Caused by: org.apache.cassandra.exceptions.ConfigurationException: Unknown host
        at org.apache.cassandra.locator.PropertyFileSnitch.reloadConfiguration(
        at org.apache.cassandra.locator.PropertyFileSnitch.<init>(
        at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
        at sun.reflect.NativeConstructorAccessorImpl.newInstance(
        at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(
        at java.lang.reflect.Constructor.newInstance(
        at java.lang.Class.newInstance(
        at org.apache.cassandra.utils.FBUtilities.construct(
        ... 6 more
Caused by: unknown error
        at Method)
        at org.apache.cassandra.locator.PropertyFileSnitch.reloadConfiguration(
        ... 13 more

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

View raw message