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 defin
should be the same version. i did notice some extra files in my etc
dir. there's a few dpkg-new files.
ubuntu@ip-10-40-207-151:~/datastax_ami$ ll /etc/cassandra/
total 100
drwxr-xr-x 2 root root 4096 2012-07-02 18:13 ./
drwxr-xr-x 99 root root 4096 2012-07-02 16:31 ../
-rw-r--r-- 1 root ro
no, it's there... after editing the first couple lines of the config
file there spot where it complains changes.
On 7/2/2012 10:20 AM, Robin Verlangen wrote:
Your missing the "sliced_buffer_size_in_kb" property in your
cassandra.yaml file.
2012/7/2 Deno Vichas mailto:d...@syncopated.net>>
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" prop
Your missing the "sliced_buffer_size_in_kb" property in your cassandra.yaml
file.
2012/7/2 Deno Vichas
> 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 v
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 AbstractCassandraDa
