Re: RFC: Cassandra Virtual Nodes

> > Does the new scheme still require the node to re-iterate all sstables to > build the merkle tree or streaming data for partition level > repair and move? You would have to iterate through all sstables on the system to repair one vnode, yes: but building the tree for just one range of the data

Re: Status of deploy to maven central patch

I would be +1 on this. We need a good way to develop against snapshots. Thanks for your work here Stephen. Stu On Fri, Mar 25, 2011 at 5:35 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Just an FYI. > > I have the required fixes for Maven ANT Tasks in place: > > http://jira.co

Re: [VOTE] 0.7.1 (what are we at now, 4?)

+1 Passes the distributed tests. On Thu, Feb 10, 2011 at 9:52 AM, Eric Evans wrote: > > I propose the following for release as 0.7.1. > > SVN: > https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1069461 > 0.7.1 artifacts: http://people.apache.org/~eevans > > The vote will be op

Re: plugins/triggers/coprocessors

Honestly, I think we should just mark 1016 a dupe and move forward with 1311: we won't be hurting anyone's feelings, and the implementation from 1016 is: 1. much, much less complete, 2. abandoned. On Fri, Feb 11, 2011 at 9:23 AM, Jeremy Hanna wrote: > Thanks Maxim - I'll just go ahead and BCC yo

Re: [VOTE] 0.7.1 (attempt #2)

-1 Kelvin was kind enough to confirm that ALL is broken in this release and trunk. See https://issues.apache.org/jira/browse/CASSANDRA-2094 On Sun, Jan 30, 2011 at 5:24 PM, Stu Hood wrote: > -0 > Upgrading from 0.7.0 to these artifacts was fine, but the write ONE read > ALL distrib

Re: [VOTE] 0.7.1 (attempt #2)

-0 Upgrading from 0.7.0 to these artifacts was fine, but the write ONE read ALL distributed test times out in an unexpected location, with no error messages on the server. The test looks valid, but is also failing in 0.8/trunk. I'll try and bisect it tomorrow from CASSANDRA-1964 (which passed cons

Re: ant build-distributed-test is broken

The Whirr dependency is a snapshot, but it is being pulled from the Twitter repo defined in ivysettings.xml. When 0.3.0 is released we'll be able to get it Maven Central. On Sat, Jan 22, 2011 at 12:40 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > On 22 January 2011 08:20, Steph

Re: Avro in the Cassandra core

It's impossible to argue against this kind of consensus, so I won't. Can we please turn this discussion to something productive? Namely: now that we've eliminated the top (IMO) choice for a standard serialization framework within Cassandra, which option _will_ we choose? Continuing down our curren

Re: Time for 1.0

> In that environment, I think the production grade validation is important. A bump in version number does not give you production grade validation: in fact, it is the other way around. I'm -1 on going to 1.0 for the next release. On Thu, Jan 13, 2011 at 9:06 AM, Eric Evans wrote: > On Thu, 201

Re: [VOTE RESULTS] was: [VOTE] 7.0

Congratulations everyone! On Sun, Jan 9, 2011 at 4:21 PM, Eric Evans wrote: > On Thu, 2011-01-06 at 11:17 -0600, Eric Evans wrote: > > SVN: > > > https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0@r1055934 > > 0.7.0 artifacts: http://people.apache.org/~eevans > > > > The vote wi

Re: Multi-tenancy, and authentication and authorization

> (1) has the problem of multiple memtables (a large amount just isn't viable There are some very straightforward solutions to this particular problem: I wouldn't rule out running with a very large number of keyspace/columnfamilies given some minor changes. As Brandon said, some of the folks that

Re: [VOTE] 0.7.0 rc3

Nick and I discovered https://issues.apache.org/jira/browse/CASSANDRA-1895last night. If someone can reproduce it, it is likely worth delaying this RC for. On Tue, Dec 21, 2010 at 5:22 PM, Eric Evans wrote: > > We've had lots of changes[1] since RC2, too many to move to release > without wider t

Re: CASSANDRA-1472 (bitmap indexes)

onathan Ellis wrote: > Is it worth testing 0.7-branch-without-1472 to make sure of that? > > On Fri, Nov 12, 2010 at 10:28 AM, Stu Hood wrote: > > Great, thanks for the variable Dragos: I'm fairly sure I broke this in > the > > refactoring I did in 1472 to fit in a sec

Re: CASSANDRA-1472 (bitmap indexes)

he KEYS_BITMAP > indexes: time out/succeed on the same queries. > > By the way, the insert of my data set with KEYS_BITMAP is much faster than > KEYS (about 5.5 times) and less gc intensive. > > Dragos > > On Tue, Nov 9, 2010 at 8:05 PM, Stu Hood wrote: > > > Intere

Re: [VOTE] 0.6.8 RC1

-1 1722 was just backported to the 0.6 branch (r1034172): I think we'll need to reroll... sorry! https://issues.apache.org/jira/browse/CASSANDRA-1722 On Thu, Nov 11, 2010 at 4:51 PM, Eric Evans wrote: > On Thu, 2010-11-11 at 14:44 -0600, Jo

RE: MerkleTree.RowHash maybe a bug.

At first glance, this appeared to be a very egregious bug, but the effect is actually minimal: since the size of the buffer is deterministic based on the size of the data, you will have equal amounts of excess/junk data for equal rows. Combined with the fact that 0.6 doesn't reuse these buffers,

Re: CASSANDRA-1472 (bitmap indexes)

if combining columns with cardinalities: 22 + 17 => no exception 22 + 10 => no exception 10 + 17 => timed out exception 22 + 17 + 10 => timed out exception On Tue, Nov 9, 2010 at 6:29 PM, Stu Hood wrote: > Can you tell me a little bit about your key distribution? How many uniq

Re: CASSANDRA-1472 (bitmap indexes)

and couldn't do any compaction. But I'm still not able to run my tests: TimedOutException :( On Tue, Nov 9, 2010 at 5:51 PM, Stu Hood wrote: > Hmm, 500 sstables is definitely a degenerate case: did you disable > compaction? By default, Cassandra strives to keep the sstable count bel

Re: CASSANDRA-1472 (bitmap indexes)

duced to just 7. Initially the compaction thread suffered the same problem of "too many open files" and couldn't do any compaction. But I'm still not able to run my tests: TimedOutException :( On Tue, Nov 9, 2010 at 5:51 PM, Stu Hood wrote: > Hmm, 500 sstables is definit

Re: CASSANDRA-1472 (bitmap indexes)

th slice size of 1. Is my machine too small (core 2 duo 2.93 2GB RAM Ubuntu 10.04) for such a test? I really have some interesting sets of data to test indexes with and I want to make a comparison between ordinary indexes and bitmap indexes. Thank you, Dragos On Mon, Nov 8, 2010 at 6:42 PM, S

RE: CASSANDRA-1472 (bitmap indexes)

Dragos, How many SSTables did you have on disk, and were any of your index expressions GT(E)/LT(E)? I expect that you are bumping into a limitation of the current implementation: it opens up to 128 file-handles per SSTable in the worst case for a GT/LT query (one per index bucket). A future v

Re: more info CASSANDRA-1472

nk you! On Mon, Nov 1, 2010 at 6:50 AM, Stu Hood wrote: > I can't reproduce this, but I've posted a rebased version on #1472 that you > can try out. Thanks for trying it out! > > > -Original Message- > From: "dragos cernahoschi" > Sent: Friday,

RE: more info CASSANDRA-1472

I can't reproduce this, but I've posted a rebased version on #1472 that you can try out. Thanks for trying it out! -Original Message- From: "dragos cernahoschi" Sent: Friday, October 29, 2010 10:38am To: dev@cassandra.apache.org Subject: more info CASSANDRA-1472 The stress.py command:

RE: [VOTE] 0.7.0 beta3

+1 -Original Message- From: "Eric Evans" Sent: Thursday, October 28, 2010 10:55am To: dev@cassandra.apache.org Subject: [VOTE] 0.7.0 beta3 The RC1 vote[1] was vetoed due to, (among other things), the desire to see more testing after the somewhat disruptive changes made in CASSANDRA-1367

Re: NoSQL, YesCQL?

Let me preface this by saying: the fact that it looks like SQL doesn't bother me. But: I think this would be a terrible thing to _focus_ on. Something for contrib? Sure. Most reasonable languages these days have a way to define what looks like a DSL: giving people a text DSL which is subject to

Re: [VOTE] 0.7.0 RC1

arning if that's not what their 0.6 value was. On Sat, Oct 23, 2010 at 2:08 PM, Stu Hood wrote: > Ack. This was a framed transport problem... the config converter will leave > people in a state where the cli won't connect by default. I guess it's a > known issue. > >

Re: [VOTE] 0.7.0 RC1

Ack. This was a framed transport problem... the config converter will leave people in a state where the cli won't connect by default. I guess it's a known issue. Sorry! -Original Message----- From: "Stu Hood" Sent: Saturday, October 23, 2010 2:03pm To: dev@cassandr

Re: [VOTE] 0.7.0 RC1

And as the last variable, the src artifact builds and does not exhibit the problem, so this is very likely a problem with the classes in the bin artifact. -Original Message- From: "Stu Hood" Sent: Saturday, October 23, 2010 1:59pm To: dev@cassandra.apache.org Subject: Re: [V

Re: [VOTE] 0.7.0 RC1

ndra-cli --host localhost Connected to: "Test Cluster" on localhost/9160 [defa...@unknown] create keyspace Keyspace1 80379cab-ded6-11df-b235-e700f669bcfc On Sat, Oct 23, 2010 at 11:44 AM, Stu Hood wrote: > Also, client connections fail immediately with a version mismatch: something >

RE: [VOTE] 0.7.0 RC1

eadMessageBegin, old client? -Original Message- From: "Eric Evans" Sent: Saturday, October 23, 2010 11:49am To: dev@cassandra.apache.org Subject: RE: [VOTE] 0.7.0 RC1 On Sat, 2010-10-23 at 11:44 -0500, Stu Hood wrote: > Also, client connections fail immediately with a vers

RE: [VOTE] 0.7.0 RC1

Also, client connections fail immediately with a version mismatch: something is not kosher with the Thrift build. Poor cats. -Original Message- From: "Stu Hood" Sent: Saturday, October 23, 2010 11:28am To: dev@cassandra.apache.org Subject: RE: [VOTE] 0.7.0 RC1 -1 bin/config

RE: [VOTE] 0.7.0 RC1

-1 bin/config-converter failed: see https://issues.apache.org/jira/browse/CASSANDRA-1655 -Original Message- From: "Eric Evans" Sent: Friday, October 22, 2010 10:28pm To: dev@cassandra.apache.org Subject: [VOTE] 0.7.0 RC1 We're closing in on a final; it shouldn't be long now. I propos

RE: [VOTE] 0.7.0 beta2 (attempt #3)

+1 Tested upgrades from 0.6.5 and 0.7-beta1. -Original Message- From: "Eric Evans" Sent: Tuesday, September 28, 2010 12:37pm To: dev@cassandra.apache.org Subject: [VOTE] 0.7.0 beta2 (attempt #3) >> It feels like 0.7.0-beta1 is becoming too distant a spec in >> the rear-view, and the delt

RE: cassandra disk usage

Also, see: https://issues.apache.org/jira/browse/CASSANDRA-1207 -Original Message- From: "Terje Marthinussen" Sent: Monday, August 30, 2010 6:58am To: dev@cassandra.apache.org Subject: cassandra disk usage Hi, Was just looking at a SSTable file after loading a dataset. The data load has

Re: launch failure with current git (svn?)

Hey Chip, Sorry for the trouble! Jon has a patch on https://issues.apache.org/jira/browse/CASSANDRA-891 that fixes this issue, and should make it in tomorrow. Thanks, Stu -Original Message- From: "Jonathan Ellis" Sent: Wednesday, August 25, 2010 9:33pm To: dev@cassandra.apache.org Sub

RE: [VOTE] 0.7.0-beta1

+1 Artifacts look good! -Original Message- From: "Eric Evans" Sent: Tuesday, August 10, 2010 12:20pm To: dev@cassandra.apache.org Subject: [VOTE] 0.7.0-beta1 Today is the Cassandra Summit in San Francisco, the first ever. As I type this, Jonathan Ellis is at the podium delivering the k

Re: Almost time for 0.7 beta?

The are a few tickets affecting the public API that Rackspace would really like to see make it into the 0.7-beta, since they will be very difficult to apply once a mass of people have gone through the readTablesFromYaml process. In particular, we'd like to see 1066, 1237 and the portion of 1271

RE: network compatibility from 0.6 to 0.7

> So I think we should probably try to preserve compatibility in 0.7. We could probably limit the scope of our network compatibility to "steady-state" messages, aka, nothing having to do with bootstrap, repair, etc. -Original Message----- From: "Stu Hood" Sent: Thu

RE: network compatibility from 0.6 to 0.7

I feel like the next time we break network compatibility should be the last time, aka, the release when we introduce a backwards compatible RPC layer (Avro?), and implement support for dropping messages that a node can't handle. So I think we should probably try to preserve compatibility in 0.7.

Re: [VOTE] Release 0.6.2

+0 Should we have release notes for this release somewhere? NEWS.txt doesn't have an 0.6.2 section. -Original Message- From: "Gary Dusbabek" Sent: Wednesday, May 26, 2010 7:50am To: dev@cassandra.apache.org Subject: Re: [VOTE] Release 0.6.2 +1 On Mon, May 24, 2010 at 16:02, Eric Evans

Becoming a Committer

Hey gang, I'd like to begin taking steps to become a committer. I sent in a CLA a while back, but re-reading the guide, it looks like the proper first step is to get a formal invitation from the PMC. Thanks, Stu Hood @stuhood Architecture Software Developer Rackspace Hosting

Re: Is SuperColumn necessary?

Hey Ed, I've been working on a similar approach for arbitarily nested/compound column names in #998. See: http://github.com/stuhood/cassandra/blob/998/src/java/org/apache/cassandra/db/ColumnKey.java The goal is to provide native support and potentially (in the very long term), API support for

Re: Bootstrap source code

Nodes declare that they will be joining the ring at a particular position, which makes them a member of the 'pending ranges' set. Nodes with pending ranges are supposed to receive writes for those ranges, despite not officially owning them yet. -Original Message- From: "Roger Schildmei

RE: boonfilters

> 1. Is the only place boonfilters are used in Cassandra is when you want to > see if a particular key exists in a particular node? Each node stores a set of SSTables locally, each with a BloomFilter attached: the filters are used to check whether a particular SSTable contains information about a

RE: Grep for what?

The actual process is `java`, which should have 'cassandra' as an argument. Make sure to use a variant of `ps` that shows the full command. -Original Message- From: "JEFFERY SCHMITZ" Sent: Monday, April 5, 2010 12:20pm To: dev@cassandra.apache.org Subject: Grep for what? Warning this i