We're also seeing something similar since upgrading to 1.0.0.
We have a 6-node cluster with replication factor of 3, but three of the
nodes are older running 32-bit Windows Server 2008, and three of the nodes
are newer and running 64-bit Windows Server 2008 R2, and we're running
32-bit java on the
Brian,
We've taken the same approach, with ElasticSearch running on the same
nodes as Cassandra.
Make sure you have enough memory on your nodes, because ElasticSearch
and Cassandra both love memory.
We started with 12gb of memory, allocating ElasticSearch and Cassandra
5gb each and it wasn
Hello,
I'm seeng the following exception during compaction. This is happening on
Linux (RHEL 6) running Cassandra 1.0. This particular instance is with
Leveled compaction, but we have seen this error in the past with SizeTiered
compaction as well. We are not using compression.
Any ideas on what m
Hi,
Im currently experimenting with Cassandra on a single node using phpcassa and
im having issues when trying to update data in existing columns. I can write
new columns/rows etc no problem however when updating I get no errors back and
the update does not occur. I've also tried updating ma
It sounds like you're looking at different rows in the CLI compared to
phpcassa and Cassandra Cluster Admin. My guess is that this is due to the
CLI using a hex encoding by default:
http://stackoverflow.com/questions/4662940/cassandra-cli-returning-weird-code
On Mon, Oct 24, 2011 at 7:23 AM, Sam
Hello all,
Right now, I have 10 machines running Cassandra 0.8.7, and mostly they are
working fine. However, during a nodetool repair of one machine, I'm seeing:
ERROR [AntiEntropySessions:12] 2011-10-24 11:17:52,154
AbstractCassandraDaemon.java (line 139) Fatal exception in thread
Thread[Anti
What is the difference between these JMX column family attributes:
TotalDiskSpaceUsed and LiveDiskSpaceUsed
Thanks!
Rene
On Mon, Oct 24, 2011 at 6:23 PM, Scott Fines wrote:
> Hello all,
> Right now, I have 10 machines running Cassandra 0.8.7, and mostly they are
> working fine. However, during a nodetool repair of one machine, I'm seeing:
> ERROR [AntiEntropySessions:12] 2011-10-24 11:17:52,154
> AbstractCassandraDa
Created https://issues.apache.org/jira/browse/CASSANDRA-3400
Thanks for your help,
Scott Fines
From: Sylvain Lebresne [sylv...@datastax.com]
Sent: Monday, October 24, 2011 11:37 AM
To: user@cassandra.apache.org
Subject: Re: ConcurrentModificationException
We are setting up my application around Cassandra .8.0 (will move to
Cassandra 1.0 in the near future). In production the application will
be running in a two (or more) node cluster with RF 2. In development,
we do not always have 2 machines to test on, so we may have to run a
Cassandra cluster con
On Mon, Oct 24, 2011 at 6:26 PM, Rene Kochen
wrote:
> What is the difference between these JMX column family attributes:
>
>
>
> TotalDiskSpaceUsed and LiveDiskSpaceUsed
Prior to Cassandra 1.0, obsolete data files (compacted ones) were not
deleted right away,
but potentially quite some times aft
On 10/24/2011 05:23 AM, Sam Hodgson wrote:
I can write new columns/rows etc no problem however when updating I
get no errors back and the update does not occur. I've also tried
updating manually using the Cassandra cluster admin gui and the same
thing happens. I can write but updates do not wo
unsubscribe
>
> unsubscribe
>
>
unsubscribe
On 10/24/2011 09:16 PM, hwj383 wrote:
unsubscribe
Send that email to
user-unsubscr...@cassandra.apache.org
I currently use buf.getLong(0), assuming the current position is 0.
(instead of using buf.getLong(buf.getPosition()) )
my code seems to be working fine. - I even added just now a check
to throw an exception if the position is not 0.
but I think I have seen cases where the position is no zero
Hello, I'm writing CassandraCli wiki page draft (sorry to late,
aaron), and found 2 problems in schema-sample.txt shipped with 1.0.0
release.
cassandra-cli prints following warning and error on loading the schema.
WARNING: [{}] strategy_options syntax is deprecated, please use {}
a0f41dc0-feba-11
Konstantin,
You can modify the RF of the keyspace with following command in cassandra-cli:
update keyspace KEYSPACE_NAME with storage_options = {replication_factor:N};
When you decrease RF, you need to run nodetool clean on each node.
When you increase RF, you need to run nodetool repair on ea
Hello, I'm writing CassandraCli wiki page draft (sorry to late,
aaron), and found 2 problems in schema-sample.txt shipped with 1.0.0
release.
cassandra-cli prints following warning and error on loading the schema.
WARNING: [{}] strategy_options syntax is deprecated, please use {}
a0f41dc0-feba-11
21 matches
Mail list logo