Hi,
I Installed Cassandra 0.8.4 on two systems configure like below
System 1: IP "10.1.1.1" which is acting as seed
- seeds: "10.1.1.1"
listen_address: 10.1.1.1
rpc_address: 10.1.1.1
System 2: IP "10.1.1.2" which is acting as node
- seeds: "10.1.1.1"
listen_address: 10.1.1.2
What was the replication factor for the keyspace ?
If it was 1 that sounds like reasonable behavior. Try increasing the RF to 2.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 12/09/2011, at 8:24 PM, RAJASHEKAR REDDY wrote:
>
I am using 0.7.4. so it is always okay to do the routine repair on
Column Family basis? thanks!
On Fri, Sep 9, 2011 at 3:25 PM, Sylvain Lebresne wrote:
>
> On Fri, Sep 9, 2011 at 4:18 AM, Yan Chunlu wrote:
> > I have 3 nodes and RF=3. I tried to repair every node in the cluster by
> > using "
Hi,
I've checked the memtable flush (cassandra 0.8.4) and it seams to me it
hapens sooner then the threshold is reached.
Here's the threshould's (the default ones calculated for a heap size of
-Xmx1980M):
ColumnFamily: idx_graphable (Super)
Key Validation Class: org.apache.cassandra.d
Hi,
We have an issue to search over Cassandra and we are using Sphinx for
indexing.
Because of Sphinx architecture we can't use range queries over all fields
that we need to.
So we have to run Sphinx Query first to get List of rowKeys and perform
additional range filtering over column values.
Fir
see memtable_total_space_in_mb at
http://thelastpickle.com/2011/05/04/How-are-Memtables-measured/
On Mon, Sep 12, 2011 at 6:55 AM, Sorin Julean wrote:
> Hi,
>
> I've checked the memtable flush (cassandra 0.8.4) and it seams to me it
> hapens sooner then the threshold is reached.
>
> Here's the
Thanks Jonathan !
memtable_total_space_in_mb is the threshold that is reached.
Kind regards,
Sorin
On Mon, Sep 12, 2011 at 3:16 PM, Jonathan Ellis wrote:
> see memtable_total_space_in_mb at
> http://thelastpickle.com/2011/05/04/How-are-Memtables-measured/
>
> On Mon, Sep 12, 2011 at 6:55 AM,
Version=0.7.8
I have a 3 node cluster with RF=3, how would I move data from a live
node to a replacement node?
I tried an autobootstrap + decomission, but I got this error on the live node:
Exception in thread "main" java.lang.IllegalStateException:
replication factor (3) exceeds number of endpo
On Sat, Sep 3, 2011 at 8:26 PM, Kevin Burton wrote:
> The point is that replication in Cassandra only needs timestamps to handle
> out of order writes … for values that are idempotent, this isn't necessary.
> The order doesn't matter.
>
I believe this is a mis-understanding of how idempotency a
Yeah - I would bootstrap at initial_token of -1 the current one. Then once
that has bootstrapped, then decommission the old one. Avoid trying to use
removetoken on anything before 0.8.3. Use decommission if you can if you're
dealing with a live node.
On Sep 12, 2011, at 10:42 AM, Kyle Gibson
> I am using 0.7.4. so it is always okay to do the routine repair on
> Column Family basis? thanks!
It's "okay" but won't do what you want; due to a bug you'll see
streaming of data for other column families than the one you're trying
to repair. This will be fixed in 1.0.
--
/ Peter Schuller (@
After writing my message, I recognized a scenerio you might be referring to
Kevin.
If I understand correctly, you're not referring to set-membership in the
general sense, where one could add and remove entries. General
set-membership, in the context of eventual-consistency, requires timestamps.
Th
This relates to the issue i opened the other day:
https://issues.apache.org/jira/browse/CASSANDRA-3175 .. basically,
'nodetool ring' throws an exception on two of the four nodes.
In my fancy little world, the problems appear to be related to one of
the nodes thinking that someone is their neighbo
What could you do if the initial_token is 0?
On Mon, Sep 12, 2011 at 1:09 PM, Jeremy Hanna
wrote:
> Yeah - I would bootstrap at initial_token of -1 the current one. Then once
> that has bootstrapped, then decommission the old one. Avoid trying to use
> removetoken on anything before 0.8.3. U
The ring wraps around, so the value before 0 is the max possible token. I
believe that it is 2**127 -1 .
- Original Message -
From: "Kyle Gibson"
To: user@cassandra.apache.org
Sent: Monday, September 12, 2011 3:30:20 PM
Subject: Re: Replace Live Node
What could you do if the initial_tok
I believe you'd need 2^127 - 1, which is 170141183460469231731687303715884105727
On Sep 12, 2011, at 2:30 PM, Kyle Gibson wrote:
> What could you do if the initial_token is 0?
>
> On Mon, Sep 12, 2011 at 1:09 PM, Jeremy Hanna
> wrote:
>> Yeah - I would bootstrap at initial_token of -1 the curren
While it would certainly be preferable to not run a cleanup and a move at
the same time on the same node, is there a techincal problem with running a
nodetool move on a node while a cleanup is running? Or if its possible to
gracefully kill a cleanup, so that a move can be run and then cleanup r
So to move data from node with token 0, the new node needs to have
initial token set to 170141183460469231731687303715884105727 ?
Another idea: could I move token to 1, and then use token 0 on the new node?
On Mon, Sep 12, 2011 at 3:38 PM, Jeremy Hanna
wrote:
> I believe you'd need 2^127 - 1, wh
> So to move data from node with token 0, the new node needs to have
> initial token set to 170141183460469231731687303715884105727 ?
I would do this route.
> Another idea: could I move token to 1, and then use token 0 on the new node?
nodetool move prior to 0.8 is a very heavy operation.
We are running the datastax .8 rpm distro. We have a situation where we
have 4 nodes and each owns 25% of the keys. However the last node in the
ring does not seem to be getting much of a load at all.
We are using the random partitioner, we have a total of about 20k keys that
are sequential...
Just checking, you want an API call like this ?
multiget_filtered_slice(keys, column_parent, predicate, filter_clause,
consistency_level)
Where filter_clause is an IndexClause.
It's a bit messy.
is there no way to express this as a single get_indexed_slice() call? With a ==
index expressio
Looks kind of like the 4th node was added to the cluster w/o bootstrapping.
On Mon, Sep 12, 2011 at 3:59 PM, David McNelis
wrote:
> We are running the datastax .8 rpm distro. We have a situation where we
> have 4 nodes and each owns 25% of the keys. However the last node in the
> ring does not
Auto-bootstrapping is turned on and the node had been started several hours
ago. Since the node already shows up as part of the ring I would imagine
that nodetool join wouldn't do anything.Is there a command to jumpstart
bootstrapping?
On Mon, Sep 12, 2011 at 4:22 PM, Jonathan Ellis wrote:
On Mon, Sep 12, 2011 at 1:44 PM, Peter Schuller
wrote:
>> I am using 0.7.4. so it is always okay to do the routine repair on
>> Column Family basis? thanks!
>
> It's "okay" but won't do what you want; due to a bug you'll see
> streaming of data for other column families than the one you're trying
Something like this.
Actually I think it's better to extend get_indexed_slice() API instead of
creating new one thrift method.
I wish to have something like this:
//here we run query to external search engine
List keys = performSphinxQuery(someFullTextSearchQuery);
IndexClause indexClause = new I
Hello everyone, I wanted to tell you about some performance
benchmarking we have done with Cassandra running in EC2 on a virtual
network.
The purpose of the experiment was to see how running Cassandra on a
virtual network could simplify operational complexity and to determine
the performance impac
I'm pretty sure I'm behind on how to deal with this problem.
Best I know is to start the node with "-Dcassandra.load_ring_state=false" as a
JVM option. But if the ghost IP address is in gossip it will not work, and it
should be in gossip.
Does the ghost IP show up in nodetool ring ?
Anyone k
> is there a techincal problem with running a nodetool move on a node while a
> cleanup is running?
Cleanup is removing data that the node is no longer responsible for while move
is first removing *all* data from the node and then streaming new data to it.
I'd put that in the crossing the s
Try a reapir on 100.5 , it will then request the data from the existing nodes.
You will then need to clean on the existing three nodes once the repair has
completed.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 13/09/2011, a
use system;
del LocationInfo[52696e67];
i ran this on the nodes that had the problems. stopped, started the
nodes, it re-did it's job job done. all fixed with a new bug!
https://issues.apache.org/jira/browse/CASSANDRA-3186
On Tue, Sep 13, 2011 at 2:09 AM, aaron morton wrote:
> I'm pretty
I think it is a serious problem since I can not "repair". I am
using cassandra on production servers. is there some way to fix it
without upgrade? I heard of that 0.8.x is still not quite ready in
production environment.
thanks!
On Tue, Sep 13, 2011 at 1:44 AM, Peter Schuller
wrote:
>> I a
Hi, Roshan. This is great support, amazing support; not used to it :)
Thanks for the reply.
Well I think java is installed correctly, I mean, the java -version command
works on a terminal, so the PATH env variable is correctly set, right?
I downloaded the JDK7 and put it on opt/java/ and then set
Hi,
Do you have JAVA_HOME exported? If not, can you export it and retry?
Cheers.
On Tue, Sep 13, 2011 at 8:59 AM, Hernán Quevedo
wrote:
> Hi, Roshan. This is great support, amazing support; not used to it :)
>
> Thanks for the reply.
>
> Well I think java is installed correctly, I mean, the jav
33 matches
Mail list logo
