Definitely multi thread writes...probably with a little batching (10 or so).
That's how i get my peak throughput.
Le 23 févr. 2012 04:48, Deno Vichas d...@syncopated.net a écrit :
all,
would i be better off (i'm in java land) with spawning a bunch of
threads that all add a single item to a
Thanks for the info.
Upgrade within the 1.0.x branch is simply a rolling restart, right?
Bill
On Thu, Feb 16, 2012 at 9:20 PM, Jonathan Ellis jbel...@gmail.com wrote:
CASSANDRA-3496, fixed in 1.0.4+
On Thu, Feb 16, 2012 at 8:27 AM, Bill Au bill.w...@gmail.com wrote:
I am running 1.0.2
Are there any good resources for best practices when running Cassandra
within EC2? I'm particularly interested in the security issues, when the
servers communicating w/ Cassandra are outside of EC2.
Thanks,
-Phil
Tanks for all these informations. Twitter Kestrel-Storm-Cassandra solution
looks very powerfull, scalable and well documented. I'll try to use this
solution.
Alain
2012/2/23 Milind Parikh milindpar...@gmail.com
Coolwww.countandra.org calls them cascaded counters and it will be
also based
flush_largest_memtables_at
Is designed as a safety valve, reducing it may help prevent an oom but it wont
get to the cause.
Assuming you cannot just allocate more memory to the JVM, and you are running
the default settings in cassandra-env.sh (other than the changes mentioned),
and you are
Unfortunately you can use column ranges for delete operations.
So while what you want to do is something like...
Delete 'Jack:*:*'...'Jack:*:*' from Test where KEY = friends;
You cannot do it.
You need to read and then delete by name.
Cheers
-
Aaron Morton
Freelance
General EC2 setup…
http://www.datastax.com/docs/1.0/install/install_ami
http://wiki.apache.org/cassandra/CloudConfig
Cassandra with a VPN on EC2. From memory it talks about using the VPN within
EC2.
http://blog.vcider.com/2011/09/running-cassandra-on-a-virtual-network-in-ec2/
Clients need a
30ms pauses are on the low side of normal for a 800MB young gen under
parnew. We're not going to be able to get rid of those, although it
looks like you're seeing objects in the young gen die *very* quickly,
so cutting that to say 200MB might give you shorter (and more
frequent) pauses for the
The only time I've seen nodetool be that slow is when it was talking
to a machine that was either swapping or deep into (JVM) GC storming.
On Wed, Feb 22, 2012 at 3:49 PM, Feng Qu mail...@gmail.com wrote:
We noticed that nodetool ring sometimes returns in 17-20 sec while it
normally runs in
Thanks Aaron for the indormation.
I increased the VM size to 2.4G from 1.4G. Please check my current CF in
below.
Keyspace: WCache:
Replication Strategy: org.apache.cassandra.locator.SimpleStrategy
Durable Writes: true
Options: [replication_factor:3]
Column Families:
ColumnFamily:
I have played with a test cluster, stopping cassandra on one node and
updating a row on another. I noticed a delay in delivering hinted
handoffs for which I don't know the rationale. After the node which
originally received the update noticed that the other server is up, it
waited 16 s before
On Thu, Feb 23, 2012 at 7:29 AM, Bill Au bill.w...@gmail.com wrote:
Upgrade within the 1.0.x branch is simply a rolling restart, right?
Generally, but you should always read NEWS.txt before upgrading.
--
Tyler Hobbs
DataStax http://datastax.com/
if I remember correctly, cassandra has a random delay in it so hint
deliver is staggered and does not overwhelm the just restarted node.
On 2/23/12 1:46 PM, Hontvári József Levente hontv...@flyordie.com
wrote:
I have played with a test cluster, stopping cassandra on one node and
updating a row
I recently started using Cassandra 1.0.4 and observed that it takes a lot
longer to flush the commit logs to SSTables, than was observed in versions
0.7.X and 0.8.X under constant load conditions with commitlog_sync as
periodic and commitlog_sync_period_in_ms as 1. As more data gets
retained
I've verified it in the source: deliverHintsToEndpointInternal in
HintedHandOffManager.java
Yes it add random delay before HH delivery.
2012/2/24 Todd Burruss bburr...@expedia.com:
if I remember correctly, cassandra has a random delay in it so hint
deliver is staggered and does not overwhelm
Hi,
I've finished my first model and experiments with Cassandra with result I'm
pretty happy with - so I thought I'd move on to something harder.
We have a set of data that has a large number of entities (which is our
primary search key), for each of the entities we have a smallish (100)
number
How about using a composite row key like the following:
Entity.Day1.TypeA: {col1:val1, col2:val2, . . . }
Entity.Day1.TypeB: {col1:val1, col2:val2, . . . }
.
.
Entity.DayN.TypeA: {col1:val1, col2:val2, . . . }
Entity.DayN.TypeB: {col1:val1, col2:val2, . . . }
It is better to avoid super
Hi Franc,
Or, you can consider using composite columns. It is not recommended to use
Super Columns anymore.
Best wishes,
Martin
On Thu, Feb 23, 2012 at 7:51 PM, Indranath Ghosh indrana...@gmail.comwrote:
How about using a composite row key like the following:
Entity.Day1.TypeA: {col1:val1,
On Fri, Feb 24, 2012 at 2:54 PM, Martin Arrowsmith
arrowsmith.mar...@gmail.com wrote:
Hi Franc,
Or, you can consider using composite columns. It is not recommended to use
Super Columns anymore.
Thanks,
I'll look in to composite columns
cheers
Best wishes,
Martin
On Thu, Feb 23,
On Fri, Feb 24, 2012 at 2:54 PM, Martin Arrowsmith
arrowsmith.mar...@gmail.com wrote:
Hi Franc,
Or, you can consider using composite columns. It is not recommended to use
Super Columns anymore.
Best wishes,
On first read it would seem that there is fair bit of overhead with
composite
No, I couldn't download the beta with the first link. The mirrors
returned 404 for that.
After exploring the link and I found the latter uri was worked.
So I don't think we need to wait.
2012/2/22 Sylvain Lebresne sylv...@datastax.com:
Arf, you'r right sorry.
I've fixed it (but it could take ~1
21 matches
Mail list logo
