I will look at that to understand the behavior of ONE with NTS.
Thanks.
- Pierre
-Original Message-
From: aaron morton
Date: Fri, 16 Sep 2011 10:11:30
To:
Reply-To: user@cassandra.apache.org
Subject: Re: Get CL ONE / NTS
> What I’m missing is a clear behavior for CL.ONE. I’m unsure ab
Writes already update rows that are hot in the cache when they are
sent. So in the best case this would be no better, and in the average
case (where you push out rows in the cache to make room for cold ones
from the memtable) a lot worse.
On Fri, Sep 16, 2011 at 8:40 PM, Yang wrote:
> this way w
this way we wouldn't need to get a sudden rise in read latency after flush.
or is something similar is already i there?
>
>> and updates could be scattered all over
>> before compaction?
>
> No, updates to a given row will be still be in a single sstable.
>
>
Can you please explain little more? You mean that if Level 1 file contains
range from 1-100 all the updates would still go in that file?
The link on le
How is the performance of ByteOrderedPartitioner, compared to
RandomPartitioner? the perforamnce when getting data with single key, does
it use same algorithm?
I have read that the downside of ByteOrderedPartitioner is creating hotspot.
But if I have 4 nodes and I set RF to 4, that will replicate
use zookeeper. Scott Fines has a great library on top of zk.
On Fri, Sep 16, 2011 at 7:08 PM, Daning Wang wrote:
> We try to implement an ordered queue system in Cassandra(ver 0.8.5). In
> initial design we use a row as queue, a column for each item in queue.
> that means creating new column w
We try to implement an ordered queue system in Cassandra(ver 0.8.5). In
initial design we use a row as queue, a column for each item in queue.
that means creating new column when inserting item and delete column when
top item is popped. Since columns are sorted in Cassandra we got the ordered
qu
Did you create a ticket?
On Fri, Sep 16, 2011 at 12:50 PM, buddhasystem wrote:
> Well, the problem is still there, i.e. I tried to add one more index and the
> 3-node cluster is just going spastic, becomes unresponsive etc. These boxes
> have plenty of CPU and memory.
>
>
> --
> View this message
Hi,
Is there a tool which imports data from large CSV files into Cassandra using
Thrift API (If using JAVA, it would be great).
Thanks,
Nehal Mehta
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/import-data-into-cassandra-tp4627325p6801723.html
Well, the problem is still there, i.e. I tried to add one more index and the
3-node cluster is just going spastic, becomes unresponsive etc. These boxes
have plenty of CPU and memory.
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/Performance-de
On Fri, Sep 16, 2011 at 9:42 AM, Yan Chunlu wrote:
> I am running local tests about upgrade cassandra. upgrade from 0.7.4 to
> 0.8.5
> after upgrade one node1, two problem happened:
> 1, node2 keep saying:
> "Received connection from newer protocol version. Ignorning message."
> is that normal
You might need to do the nodetool scrub on the nodes to rebuild the sstables
for the different protocols.
On Fri, Sep 16, 2011 at 10:50 PM, Yan Chunlu wrote:
> and also the load is unusual(node1 has 80M data before the upgrade):
>
> bash-3.2$ bin/nodetool -h localhost ring
> Address DC
and also the load is unusual(node1 has 80M data before the upgrade):
bash-3.2$ bin/nodetool -h localhost ring
Address DC RackStatus State LoadOwns
Token
93798607613553124915572813490354413064
node2 datacenter1 rack1 Up Normal 86.03 MB
after kill node1 and start it again, node 3 has the same problems with
node2...
On Fri, Sep 16, 2011 at 10:42 PM, Yan Chunlu wrote:
> I am running local tests about upgrade cassandra. upgrade from 0.7.4 to
> 0.8.5
> after upgrade one node1, two problem happened:
>
> 1, node2 keep saying:
>
>
I am running local tests about upgrade cassandra. upgrade from 0.7.4 to
0.8.5
after upgrade one node1, two problem happened:
1, node2 keep saying:
"Received connection from newer protocol version. Ignorning message."
is that normal behaviour?
2, while running "describe cluster" on node1, it
The example works against the 7.0 branch, not against trunk.
JIRA created at https://issues.apache.org/jira/browse/CASSANDRA-3215
On Thu, Sep 15, 2011 at 3:58 PM, Tharindu Mathew wrote:
> Now I get this,
>
> Any help would be greatly appreciated.
>
> ./bin/word_count
> 11/09/15 12:28:28 INFO Wor
On Thu, Sep 15, 2011 at 10:04 PM, mcasandra wrote:
> This is a great new! Is it possible to do a write-up of main changes like
> "Leveldb" and explain it a little bit. I get lost reading JIRA and sometimes
> is difficult to follow the thread. It looks like there are some major
> changes in this re
17 matches
Mail list logo
