You can have a look at Achilles, it's using the Java Driver underneath :
https://github.com/doanduyhai/Achilles
Le 8 juin 2014 04:24, Kevin Burton bur...@spinn3r.com a écrit :
Looks like the java-driver is working on an object mapper:
More modules including a simple object mapper will come
You do not Need RAID0 for data. Let C* do striping over data disks.
And maybe CL ANY/ONE might be sufficient for your writes.
Am 08.06.2014 um 06:15 schrieb Kevin Burton bur...@spinn3r.com:
we're using containers for other reasons, not just cassandra.
Tightly constraining resources
I am using Cassandra 1.1 (sorry bit old) and I am seeing high pending
compaction count. pending tasks: 67 while active compaction tasks are not
more than 5. I have a 24CPU machine. Shouldn't I be seeing more compactions? Is
this a pattern of high writes and compactions backing up? How can I
23
On Sunday, June 8, 2014, S C as...@outlook.com wrote:
I am using Cassandra 1.1 (sorry bit old) and I am seeing high pending
compaction count. pending tasks: 67 while active compaction tasks are
not more than 5. I have a 24CPU machine. Shouldn't I be seeing more
compactions? Is this a
Have you verified that these aren't stuck compactions? e.g. even under
no load, they don't go away?
-Bill
On 06/08/2014 12:32 PM, Jake Luciani wrote:
23
On Sunday, June 8, 2014, S C as...@outlook.com
mailto:as...@outlook.com wrote:
I am using Cassandra 1.1 (sorry bit old) and I am
How to check if there are any stuck compactions?
Date: Sun, 8 Jun 2014 12:43:45 -0400
From: wkat...@cs.rutgers.edu
To: user@cassandra.apache.org
Subject: Re: high pending compactions
Have you verified that these aren't stuck compactions? e.g. even under
no load, they don't go away?
Here’s the Jira for the proposal to remove BOP (and OPP), but you can see that
there is no clear consensus and that the issue is still open:
CASSANDRA-6922 - Investigate if we can drop ByteOrderedPartitioner and
OrderPreservingPartitioner in 3.0
Hey Jack. Thanks for posting this… very helpful.
So I guess the status is that it was proposed for deprecation but that
proposal didn't reach consensus.
Also, this gave me an idea to look at the JIRA to see what's being
proposed for 3.0 :)
Kevin
On Sun, Jun 8, 2014 at 1:26 PM, Jack
Hi everyone,
We are running some Cassandra clusters (Usually a cluster of 5 nodes with
replication factor of 3.) And at least once per day we do see some corruption
related to a specific sstable in system/hints. (We are using Cassandra version
1.2.16 on RHEL 6.5)
Here is an example of such
Kevin,
We are about to release 2.0 of https://github.com/savoirtech/hecate
It is an ASL licensed library that started with Jeff Genender writing a Pojo
library in Hector for a project we did for Ecuador (Essentially all of Ecuador
uses this).
I extended this with Pojo Graph stuff like
I would check out spring Cassandra-most of the java drivers out there for
Cassandra offer very little over the new 2. driver from Datastax. Or just use
the java driver 2. as is.
There's even a query builder light fluent DSL if you don't like cql. Based
upon your use case description so far,
I wasn't responding as a Datastax employee.
I have used hector, Achilles and a few others as well. The .net drivers used
to have an edge, but that is evaporating as well.
I have also built my own mapping layers.
But all if that was when the drivers from Datastax weren't there yet.
Yes, I
So - you deduced that we were not using the driver,
were not datstax friendly and we'd be paying for this down the road?
On Jun 8, 2014, at 9:05 PM, Colin colpcl...@gmail.com wrote:
I wasn't responding as a Datastax employee.
I have used hector, Achilles and a few others as well. The .net
On a second reply I'll provide some docs.
We looked at Astynax (Yeah I didn't like the refactor)
We looked at spring - Are you fucking kidding me?
We have done quite a bit of work in the ORM arena.
* I passionately hate the idea of CQL. *
So - I told myself, I need to make this work so I never
Sounds like you've done some great work. But I still think it's a good idea
for people new to Cassandra establish a base line so that they have something
to compare other approaches against.
It sounds like we potentially have different views in this regard, but are
still interested in the
15 matches
Mail list logo
