You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Thomas Atwood (JIRA)" <ji...@apache.org> on 2013/09/18 04:21:52 UTC

[jira] [Comment Edited] (CASSANDRA-6020) Cassandra 2.0 distribution errors on default YAML configuration

    [ https://issues.apache.org/jira/browse/CASSANDRA-6020?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13770321#comment-13770321 ] 

Thomas Atwood edited comment on CASSANDRA-6020 at 9/18/13 2:19 AM:
-------------------------------------------------------------------

Per Brandon's comment, I am not sure he has tested Cassandra 2.0.0 on a Windows machine.  Yes, cas_contention_timeout_in_ms is in the yaml file.  However, the error is that the property cannot be found on class org.apache.cassandra.config.Config.  Therefore, either the default yaml file in the 2.0.0 is incorrect and needs to be adjusted, or the class needs to be modified to include the property.  Proper resolution would be for one of the more senior project contributors to know of this issue and adjust accordingly.  It is that or I am misinterpreting the issue entirely...
                
      was (Author: tmatwood@pentucketcapital.com):
    Per Brandon's comment, I am not sure he has tested Cassandra 2.0.0 on a Windows machine.  Yes, cas_contention_timeout_in_ms is in the yaml file.  However, the error is that the property cannot be found on class org.apache.cassandra.config.Config.  Therefore, either the default yaml file in the 2.0.0 is incorrect and needs to be adjusted, or the class needs to be modified to include the property.  Proper resolution would be for one of the more senior project contributors to know of this issue and adjust accordingly.
                  
> Cassandra 2.0 distribution errors on default YAML configuration
> ---------------------------------------------------------------
>
>                 Key: CASSANDRA-6020
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6020
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Config
>         Environment: Windows 8 x64
>            Reporter: Thomas Atwood
>            Priority: Critical
>             Fix For: 2.0
>
>
> The default Cassandra 2.0.0 YAML configuration does not allow for a user to use "out of the box" due to faulty YAML configuration.
> Specifically, the server notes "Unable to find property 'cas_contention_timeout_in_ms' on class: org.apache.cassandra.config.Config
>  in 'reader', line 10, column 1:
>     cluster_name: 'DEV'"
> YAML configuration should be reviewed and adjusted.
> Detailed server output below:
> Microsoft Windows [Version 6.2.9200]
> (c) 2012 Microsoft Corporation. All rights reserved.
> C:\Users\Thomas>cassandra
> Starting Cassandra Server
>  INFO 17:14:20,336 Logging initialized
>  INFO 17:14:20,372 JVM vendor/version: Java HotSpot(TM) 64-Bit Server VM/1.6.0_31
>  WARN 17:14:20,378 Your JVM is out of date. Please upgrade to the newest Oracle Java 6.
>  INFO 17:14:20,380 Heap size: 1060372480/1060372480
>  INFO 17:14:20,380 Classpath: C:\Cassandra\\conf;C:\Cassandra\\lib\antlr-3.2.jar;C:\Cassandra\\lib\apache-cassandra-1.2.9.jar;C:\Cassandra\\lib\apache-cassandra
> -2.0.0.jar;C:\Cassandra\\lib\apache-cassandra-clientutil-1.2.9.jar;C:\Cassandra\\lib\apache-cassandra-clientutil-2.0.0.jar;C:\Cassandra\\lib\apache-cassandra-th
> rift-1.2.9.jar;C:\Cassandra\\lib\apache-cassandra-thrift-2.0.0.jar;C:\Cassandra\\lib\avro-1.4.0-fixes.jar;C:\Cassandra\\lib\avro-1.4.0-sources-fixes.jar;C:\Cass
> andra\\lib\commons-cli-1.1.jar;C:\Cassandra\\lib\commons-codec-1.2.jar;C:\Cassandra\\lib\commons-lang-2.6.jar;C:\Cassandra\\lib\compress-lzf-0.8.4.jar;C:\Cassan
> dra\\lib\concurrentlinkedhashmap-lru-1.3.jar;C:\Cassandra\\lib\disruptor-3.0.1.jar;C:\Cassandra\\lib\guava-13.0.1.jar;C:\Cassandra\\lib\high-scale-lib-1.1.2.jar
> ;C:\Cassandra\\lib\jackson-core-asl-1.9.2.jar;C:\Cassandra\\lib\jackson-mapper-asl-1.9.2.jar;C:\Cassandra\\lib\jamm-0.2.5.jar;C:\Cassandra\\lib\jbcrypt-0.3m.jar
> ;C:\Cassandra\\lib\jline-1.0.jar;C:\Cassandra\\lib\json-simple-1.1.jar;C:\Cassandra\\lib\libthrift-0.7.0.jar;C:\Cassandra\\lib\libthrift-0.9.0.jar;C:\Cassandra\
> \lib\log4j-1.2.16.jar;C:\Cassandra\\lib\lz4-1.1.0.jar;C:\Cassandra\\lib\metrics-core-2.0.3.jar;C:\Cassandra\\lib\netty-3.5.9.Final.jar;C:\Cassandra\\lib\servlet
> -api-2.5-20081211.jar;C:\Cassandra\\lib\slf4j-api-1.7.2.jar;C:\Cassandra\\lib\slf4j-log4j12-1.7.2.jar;C:\Cassandra\\lib\snakeyaml-1.11.jar;C:\Cassandra\\lib\sna
> keyaml-1.6.jar;C:\Cassandra\\lib\snappy-java-1.0.5.jar;C:\Cassandra\\lib\snaptree-0.1.jar;C:\Cassandra\\lib\thrift-server-0.3.0.jar;C:\Cassandra\\build\classes\
> main;C:\Cassandra\\build\classes\thrift;C:\Cassandra\\lib\jamm-0.2.5.jar
>  INFO 17:14:20,390 JNA not found. Native methods will be disabled.
>  INFO 17:14:20,420 Loading settings from file:/C:/Cassandra/conf/cassandra.yaml
> ERROR 17:14:20,805 Fatal configuration error error
> Can't construct a java object for tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create property=cas_contention_timeout_in_ms for JavaBe
> an=org.apache.cassandra.config.Config@2e716cb7; Unable to find property 'cas_contention_timeout_in_ms' on class: org.apache.cassandra.config.Config
>  in 'reader', line 10, column 1:
>     cluster_name: 'DEV'
>     ^
>         at org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:333)
>         at org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:182)
>         at org.yaml.snakeyaml.constructor.BaseConstructor.constructDocument(BaseConstructor.java:141)
>         at org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:127)
>         at org.yaml.snakeyaml.Yaml.loadFromReader(Yaml.java:481)
>         at org.yaml.snakeyaml.Yaml.load(Yaml.java:412)
>         at org.apache.cassandra.config.DatabaseDescriptor.loadYaml(DatabaseDescriptor.java:148)
>         at org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:123)
>         at org.apache.cassandra.service.CassandraDaemon.setup(CassandraDaemon.java:217)
>         at org.apache.cassandra.service.CassandraDaemon.activate(CassandraDaemon.java:447)
>         at org.apache.cassandra.service.CassandraDaemon.main(CassandraDaemon.java:490)
> Caused by: org.yaml.snakeyaml.error.YAMLException: Cannot create property=cas_contention_timeout_in_ms for JavaBean=org.apache.cassandra.config.Config@2e716cb7;
>  Unable to find property 'cas_contention_timeout_in_ms' on class: org.apache.cassandra.config.Config
>         at org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:299)
>         at org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.construct(Constructor.java:189)
>         at org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:331)
>         ... 10 more
> Caused by: org.yaml.snakeyaml.error.YAMLException: Unable to find property 'cas_contention_timeout_in_ms' on class: org.apache.cassandra.config.Config
>         at org.yaml.snakeyaml.introspector.PropertyUtils.getProperty(PropertyUtils.java:132)
>         at org.yaml.snakeyaml.introspector.PropertyUtils.getProperty(PropertyUtils.java:121)
>         at org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.getProperty(Constructor.java:308)
>         at org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:240)
>         ... 12 more
> null; Can't construct a java object for tag:yaml.org,2002:org.apache.cassandra.config.Config; exception=Cannot create property=cas_contention_timeout_in_ms for
> JavaBean=org.apache.cassandra.config.Config@2e716cb7; Unable to find property 'cas_contention_timeout_in_ms' on class: org.apache.cassandra.config.Config;  in '
> reader', line 10, column 1:
>     cluster_name: 'DEV'
>     ^
> Invalid yaml; unable to start server.  See log for stacktrace.
> C:\Users\Thomas>cassandra

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira