you're right!

somehow while rebooting it tried to upgrade. this broke node has 1.1.1 where my others are running 1.0.7. wtf??


-  deno


On 7/2/2012 10:25 AM, Brian Jeltema wrote:
Just the opposite, I think. The property value exists in the yaml file but does not have a corresponding definition in the Config class.
Typically caused by a version mismatch in my experience.

On Jul 2, 2012, at 1:20 PM, Robin Verlangen wrote:

Your missing the "sliced_buffer_size_in_kb" property in your cassandra.yaml file.

2012/7/2 Deno Vichas <d...@syncopated.net <mailto:d...@syncopated.net>>

    i'm seeing the following exception in my log now.  this is even
    after re-creating my config file.


     INFO [main] 2012-07-02 16:58:17,850 AbstractCassandraDaemon.java
    (line 121) JVM vendor/version: Java HotSpot(TM) 64-Bit Server
    VM/1.6.0_26
     INFO [main] 2012-07-02 16:58:17,853 AbstractCassandraDaemon.java
    (line 122) Heap size: 1936719872/1937768448
     INFO [main] 2012-07-02 16:58:17,854 AbstractCassandraDaemon.java
    (line 123) Classpath:
    
/usr/share/cassandra/lib/antlr-3.2.jar:/usr/share/cassandra/lib/avro-1.4.0-fixes.jar:/usr/share/cassandra/lib/avro-1.4.0-sources-fixes.jar:/usr/share/cassandra/lib/commons-cli-1.1.jar:/usr/share/cassandra/lib/commons-codec-1.2.jar:/usr/share/cassandra/lib/commons-lang-2.4.jar:/usr/share/cassandra/lib/compress-lzf-0.8.4.jar:/usr/share/cassandra/lib/concurrentlinkedhashmap-lru-1.3.jar:/usr/share/cassandra/lib/guava-r08.jar:/usr/share/cassandra/lib/high-scale-lib-1.1.2.jar:/usr/share/cassandra/lib/jackson-core-asl-1.9.2.jar:/usr/share/cassandra/lib/jackson-mapper-asl-1.9.2.jar:/usr/share/cassandra/lib/jamm-0.2.5.jar:/usr/share/cassandra/lib/jline-0.9.94.jar:/usr/share/cassandra/lib/joda-time-1.6.2.jar:/usr/share/cassandra/lib/json-simple-1.1.jar:/usr/share/cassandra/lib/libthrift-0.7.0.jar:/usr/share/cassandra/lib/log4j-1.2.16.jar:/usr/share/cassandra/lib/metrics-core-2.0.3.jar:/usr/share/cassandra/lib/servlet-api-2.5-20081211.jar:/usr/share/cassandra/lib/slf4j-api-1.6.1.jar:/usr/share
    
/cassandra/lib/slf4j-log4j12-1.6.1.jar:/usr/share/cassandra/lib/snakeyaml-1.6.jar:/usr/share/cassandra/lib/snappy-java-1.0.4.1.jar:/usr/share/cassandra/lib/snaptree-0.1.jar:/usr/share/cassandra/apache-cassandra-1.1.1.jar:/usr/share/cassandra/apache-cassandra-thrift-1.1.1.jar:/usr/share/cassandra/apache-cassandra.jar:/usr/share/cassandra/stress.jar:/usr/share/java/jna.jar:/etc/cassandra:/usr/share/java/commons-daemon.jar:/usr/share/cassandra/lib/jamm-0.2.5.jar
     INFO [main] 2012-07-02 16:58:19,309 CLibrary.java (line 111) JNA
    mlockall successful
     INFO [main] 2012-07-02 16:58:19,319 DatabaseDescriptor.java
    (line 127) Loading settings from file:/etc/cassandra/cassandra.yaml
    ERROR [main] 2012-07-02 16:58:19,517 DatabaseDescriptor.java
    (line 481) Fatal configuration error error
    Can't construct a java object for tag:yaml.org
    <http://yaml.org/>,2002:org.apache.cassandra.config.Config;
    exception=Cannot create property=sliced_buffer_size_in_kb for
    JavaBean=org.apache.cassandra.config.Config@371bed71; Unable to
    find property 'sliced_buffer_size_in_kb' on class:
    org.apache.cassandra.config.Config
     in "<reader>", line 4, column 1:
        cluster_name: 'StockTouchCluster'
        ^

            at
    
org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:372)
            at
    
org.yaml.snakeyaml.constructor.BaseConstructor.constructObject(BaseConstructor.java:177)
            at
    
org.yaml.snakeyaml.constructor.BaseConstructor.constructDocument(BaseConstructor.java:136)
            at
    
org.yaml.snakeyaml.constructor.BaseConstructor.getSingleData(BaseConstructor.java:122)
            at org.yaml.snakeyaml.Loader.load(Loader.java:52)
            at org.yaml.snakeyaml.Yaml.load(Yaml.java:166)
            at
    
org.apache.cassandra.config.DatabaseDescriptor.loadYaml(DatabaseDescriptor.java:143)
            at
    
org.apache.cassandra.config.DatabaseDescriptor.<clinit>(DatabaseDescriptor.java:118)
            at
    
org.apache.cassandra.service.AbstractCassandraDaemon.setup(AbstractCassandraDaemon.java:126)
            at
    
org.apache.cassandra.service.AbstractCassandraDaemon.init(AbstractCassandraDaemon.java:254)
            at sun.reflect.NativeMethodAccessorImpl.invoke0(Native
    Method)
            at
    
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
            at
    
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
            at java.lang.reflect.Method.invoke(Method.java:597)
            at
    org.apache.commons.daemon.support.DaemonLoader.load(DaemonLoader.java:160)
    Caused by: org.yaml.snakeyaml.error.YAMLException: Cannot create
    property=sliced_buffer_size_in_kb for
    JavaBean=org.apache.cassandra.config.Config@371bed71; Unable to
    find property 'sliced_buffer_size_in_kb' on class:
    org.apache.cassandra.config.Config
            at
    
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:305)
            at
    
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.construct(Constructor.java:184)
            at
    
org.yaml.snakeyaml.constructor.Constructor$ConstructYamlObject.construct(Constructor.java:370)
            ... 14 more
    Caused by: org.yaml.snakeyaml.error.YAMLException: Unable to find
    property 'sliced_buffer_size_in_kb' on class:
    org.apache.cassandra.config.Config
            at
    
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.getProperty(Constructor.java:342)
            at
    
org.yaml.snakeyaml.constructor.Constructor$ConstructMapping.constructJavaBean2ndStep(Constructor.java:240)
            ... 16 more


    On 7/2/2012 9:00 AM, Deno Vichas wrote:
    the node that doesn't want to start just spit out -

        /EC2 is experiencing some issues and has not allocated all
        of the resources in under 10 minutes.
        Aborting the clustering of this reservation. Please try again.

        Please visit http://datastax.com/ami for this AMI's feature set.
        /




    On 7/2/2012 8:43 AM, Deno Vichas wrote:
    all,

    my 4 node cluster seems pretty screwed up after the AWS
    outage.  we found all our machines with their cpu stuck at
    100%.  so i went to restart each cassandra node one by one.  i
    did node with token id 0 first.  i came back but doesn't look
    like it doing anything.  once i thought it was up i went and
    restarted the next.  this one got stuck on the AMI init
    startup.  i cancelled it, rebooted againg and now it't suck
    with "[INFO] 07/02/12-15:42:29 Received 0 of 1 responses from: "

    suggestions on how to fix this?


    thanks,
    deno







--
With kind regards,

Robin Verlangen
/Software engineer/
/
/
W http://www.robinverlangen.nl <http://www.robinverlangen.nl/>
E ro...@us2.nl <mailto:ro...@us2.nl>

Disclaimer: The information contained in this message and attachments is intended solely for the attention and use of the named addressee and may be confidential. If you are not the intended recipient, you are reminded that the information remains the property of the sender. You must not use, disclose, distribute, copy, print or rely on this e-mail. If you have received this message in error, please contact the sender immediately and irrevocably delete this message and any copies.




Reply via email to