Thanks for the confirmation this is NOT the way to go. I will stick with 4
disks raid 0 with a single data directory.
On Mon, Aug 23, 2010 at 9:24 PM, Rob Coli wrote:
> On 8/22/10 12:00 AM, Wayne wrote:
>
>> Due to compaction being so expensive in terms of disk resources, does it
>> make more s
On Fri, Aug 13, 2010 at 11:15 PM, Carlos Sanchez
wrote:
> All,
>
> I was wondering if I could get some information (link / pdf) about the new
> [column] indices in Cassandra for version 0.7
>
Seconded; specifically I was wondering if you can define the secondary
indexes inside cassandra.yaml, an
Scratch that, looks like a fix is on it's way...https://issues.apache.org/jira/browse/CASSANDRA-1237 for 0.8 and https://issuesapache.org/jira/browse/CASSANDRA-1271 for 0.7AaronOn 23 Aug, 2010,at 11:39 PM, aaron morton wrote:I may try to code a fix for this as it seems like the easiest cassandra t
i am getting this as well. i am calling batch_mutate. i don't see any
server logs at INFO level. switched to DEBUG and still no interesting
messages.
by setting break points i tracked it down to TIOStreamTransport with
type TTransportException.END_OF_FILE. seems for some reason the bytes
read
On Tue, Aug 24, 2010 at 12:28 AM, aaron morton wrote:
> I think this may have been discussed before, but I cannot find any reference
> to it. Just wanted to confirm how cassandra.yaml is used after the cluster is
> initialised.
>
> Start a clean install of 0.7b1, use jconsole to import the schem
Thanks for the explanation, I'll see if I can merge that into the http://wiki.apache.org/cassandra/StorageConfigurationandhttp://wiki.apache.org/cassandra/StorageConfiguration_0.7pagesAaronOn 24 Aug, 2010,at 12:42 AM, Sylvain Lebresne wrote:The cassandra.yaml holds general configuration of cassand
On 8/11/10 10:38 AM, Ran Tavory wrote:
Due to administrative error one of the hosts in the cluster lost
permission to write to it's data directory.
So I started seeing errors in the log, however, the server continued
serving traffic. It wasn't able to compact and do other write operations
but it
On 8/22/10 12:00 AM, Wayne wrote:
Due to compaction being so expensive in terms of disk resources, does it
make more sense to have 2 data volumes instead of one? We have 4 data
disks in raid 0, would this make more sense to be 2 x 2 disks in raid 0?
That way the reader and writer I assume would a
yes, if i wait a second or two all is well. i didn't know about
"check_schema_agreement". is there a wiki page about using the new
keyspace management API? i don't see it on the Thrift API page.
i will apply the other patch you mentioned as well.
i think this is the same scenario,
https://issu
On second thought, that doesn't look like the problem at all.
Have you waited long enough for the schema to propagate? What does
check_schema_agreement tell you?
One thing to make sure about: you should funnel all your schema
updates through a single coordinator node or make sure that the
cluste
It looks like you're running into
https://issues.apache.org/jira/browse/CASSANDRA-1403, which was fixed
last week and will be included in beta2.
If you are experiencing this on trunk, please do file another ticket,
or comment on the existing one.
Gary.
On Mon, Aug 23, 2010 at 13:33, B. Todd Bur
i see the following in my server logs quite closely while doing a lot of
batch_mutations and reads. i create keyspaces and column families using
thrift api, not cassandra.yaml. did not migrate anything from 0.6.
4 node cluster, RF = 3, QUORUM read/write.
happens immediately on a fresh start of
This was a mistake, there was one node set ReplicationFactor as 3. So
Node3 has data.
On Aug 23, 2010, at 10:21 AM, Zhong Li wrote:
1) I am using RackUnwarePartioner.
2) All nodes were rebuilt since we installed the system, we didn't
do cleanup although.
But Node1's data on Node3 are n
1) I am using RackUnwarePartioner.
2) All nodes were rebuilt since we installed the system, we didn't do
cleanup although.
But Node1's data on Node3 are new data. I checked Cassandra source
code, and can't figure out yet. Here may be the case.
A NodeW write data on Node1, the FailureDetec
The cassandra.yaml holds general configuration of cassandra and the
schema definitions.
As of 0.7, the schema definition are not need anymore in this file as
schema can be defined
programatically. Those definition are are ignored by any node that
already have schema loaded
(hence the warning). But
I think this may have been discussed before, but I cannot find any reference to
it. Just wanted to confirm how cassandra.yaml is used after the cluster is
initialised.
Start a clean install of 0.7b1, use jconsole to import the schema from yaml.
Drain the node and shut it down, then remove the
I may try to code a fix for this as it seems like the easiest cassandra ticket
I could image (and my Java is a little rusty :) )
How about changing the format of the access.properties file to something like
Keyspace1=jsmith:FULL,Elvis Presley:READ,dilbert:READWRITE
If no access level specifie
17 matches
Mail list logo
