move first removes the node from the cluster, then adds it back
http://wiki.apache.org/cassandra/Operations#Moving_nodes
If you have 3 nodes and rf 3, removing the node will result in the error you
are seeing. There is not enough nodes in the cluster to implement the
replication factor.
You c
Wider rows may need to run through the slower 2-phase compaction process, see
in_memory_compaction_limit_in_mb in the yaml file. They can also result in more
GC, depending on work load etc.
Some testing I did on query performance
http://thelastpickle.com/2011/07/04/Cassandra-Query-Plans/
Ther
It will depend on your query needs, if you only need pattern matching on
strings and single (or a few) term queries I would start with a custom index.
If you need more features try https://github.com/tjake/Solandra
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmo
did you check the logs in 1.27 for errors ?
Could you be seeing this ? https://issues.apache.org/jira/browse/CASSANDRA-2867
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 7 Aug 2011, at 16:24, Dikang Gu wrote:
> I restart both
thanks for the help!
On Sun, Aug 7, 2011 at 2:10 PM, Dikang Gu wrote:
> Yes, I think you are right.
>
> The "nodetool move" will move the keys on the node to the other two nodes,
> and the required replication is 3, but you will only have 2 live nodes after
> the move, so you have the exception.
thanks for the confirmation aaron!
On Sun, Aug 7, 2011 at 4:01 PM, aaron morton wrote:
> move first removes the node from the cluster, then adds it back
> http://wiki.apache.org/cassandra/Operations#Moving_nodes
>
> If you have 3 nodes and rf 3, removing the node will result in the error
> you ar
Great!
If possible, please blog about full-text-search options + how to use
them (Solandra, Elastic Search, Sphinx etc).
Thanks!
On Sun, Aug 7, 2011 at 5:58 AM, Edward Capriolo wrote:
>
>
> On Thu, Aug 4, 2011 at 5:12 AM, Boris Yen wrote:
>
>> Looking forward to it. ^^
>>
>> On Thu, Aug 4, 2011
Great ! Thanks for the link.
On 07. 08. 11 10:10, aaron morton wrote:
Wider rows may need to run through the slower 2-phase compaction
process, see in_memory_compaction_limit_in_mb in the yaml file. They
can also result in more GC, depending on work load etc.
Some testing I did on query per
Read
On Aug 6, 2011 7:58 PM, "Edward Capriolo" wrote:
> On Thu, Aug 4, 2011 at 5:12 AM, Boris Yen wrote:
>
>> Looking forward to it. ^^
>>
>> On Thu, Aug 4, 2011 at 1:56 PM, Eldad Yamin wrote:
>>
>>> Great! I hope it will be open soon!
>>>
>>>
>>> On Wed, Aug 3, 2011 at 10:33 PM, Ed Anuff wrote
Thanks Aaron.
The first paragraph is very clear however the 2nd paragraph leaves me
wondering regarding counter columns in my setup.
I am writing at CL.ALL and reading at CL.ONE so if I get dropped messages,
it will show up as Timeouts on the client side so possibly the mutation was
not run on all
A question regarding batch mutates and how others might be throttling the
system to prevent timeouts.
My 3-node, RF=3 cluster has been performing ok while bulk loading data
(applying counter updates). I've been able to run 16 threads in parallel
that each perform about 400 mutates/s on a loaded cl
Thanks guys.
The problem is solved. I copied cassandra and cassandra.in to my bin folder.
Then used "ant release " to generate my customized cassandra.jar in dist
folder.
it worked.
To Aaron: I tried "ant artefacts", but it failed. is it because I am using
Cassandra 0.7?
What's the difference bet
hello,
I've got new errors showing up in my cassandra log file since I starting
testing batch mutates (and it failed).
I have done a rolling restart and they are not disappearing.
How can I fix this ? What is this really saying about my data and my cluster
?
Thanks
ERROR [ReplicateOnWriteStage:35
Hello,
I am trying to Setup Cassandra0.8 in Eclipse following
http://wiki.apache.org/cassandra/RunningCassandraInEclipse
After right clicking on the build.xml -> "Run As" -> "Ant Build".
Error appeared as follows:
Buildfile: /workspace/Cassandra0.8/build.xml
maven-ant-tasks-localrepo:
maven-ant-t
Quick followup.
I have pushed the RPC timeout to 30s. Using Hector, I'm doing 1 thread doing
batches of 10 mutates at a time so that's even slower than when I was doing
16 threads in parallel doing non-batched mutations.
After a couple hundred execute() calls, I get a timeout for every node; I
have
Cassandra: 0.7.8
phpcassa: 0.7.a.4
The front page of a site I manage displays a list of products
available. If a product is available, a visitor can order, otherwise
"not in stock" is displayed.
Whether the product is in stock or not is determined from the
cassandra cluster. Occasionally, but not
Maybe you could try to adjust the setting "cassandraThriftSocketTimeout" of
hector. https://github.com/rantav/hector/wiki/User-Guide
On Mon, Aug 8, 2011 at 6:54 AM, Philippe wrote:
> Quick followup.
> I have pushed the RPC timeout to 30s. Using Hector, I'm doing 1 thread
> doing batches of 10 m
Hi Aaron,
I repeat the whole procedure:
1. kill the cassandra instance on 1.27.
2. rm the data/system/Migrations-g-*
3. rm the data/system/Schema-g-*
4. bin/cassandra to start the cassandra.
Now, the migration seems stop and I do not find any error in the system.log yet.
The ring looks good:
[
Hi Boris,
Thanks for the suggestion, I didn't know there was one.
I believe have finally figured it out and it turns out my last two questions
are related.
First, my batch loading was ignoring a bunch of rows when reading the first
file (so it took hundreds of potential mutations for the problem
Make sure svn is on the PATH.
If you open a terminal (or cmd), running svn command should work.
On 07. 08. 11 23:39, Alvin UW wrote:
It seems svn wasn't installed, but i did install it.
Its
ant artifacts
Bye
Norman
2011/8/7, Alvin UW :
> Thanks guys.
>
> The problem is solved. I copied cassandra and cassandra.in to my bin folder.
> Then used "ant release " to generate my customized cassandra.jar in dist
> folder.
> it worked.
>
> To Aaron: I tried "ant artefacts", but it faile
21 matches
Mail list logo
