+1
-Chris
On May 25, 2010, at 10:25 PM, Jonathan Ellis wrote:
+1
On Mon, May 24, 2010 at 4:02 PM, Eric Evans eev...@rackspace.com wrote:
As promised, here is the 0.6.2 vote.
The list of changes from 0.6.1 is longer than I'd have liked, so it
would be great if everyone can give this
I can chime in on that part Joe. The counters weren't the reasons for launch
issues. It was just actually the volume of messages we were trying to handle in
the cluster, so it didn't matter if it was reads for counts or reads to normal
CFs, we just had more on the count side.
It is very
+1
-Chris
On Oct 31, 2010, at 8:48 PM, Stu Hood wrote:
+1
-Original Message-
From: Eric Evans eev...@rackspace.com
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
+1
-Chris
On Nov 11, 2010, at 3:39 PM, Eric Evans wrote:
A regression caused by CASSANDRA-1622[1] (and fixed in CASSANDRA-1727[2])
made its way into the last release. With that fixed now (along with an
11th hour backport of CASSANDRA-1722[3]), I propose the following
artifacts for 0.6.8.
I was looking over the Operations wiki, and with the many improvements with
0.7, I wanted to bring up a thought.
The two options today for replacing a node that has lost all data is:
(Recommended approach) Bring up the replacement node with a new IP address, and
AutoBootstrap set to true in
streamed. A node
that claims a token that is in the ring is assumed to actually have
that data and IMO trying to guess when to break that would be
error-prone -- better to have some explicit signal.
On Sun, Jan 30, 2011 at 1:38 AM, Chris Goffinet c...@chrisgoffinet.com
wrote:
I was looking
We no longer backport to 0.7. We're on 0.8/trunk at the moment.
-Chris
On Mar 23, 2011, at 9:02 PM, Robert Coli wrote:
On Wed, Mar 23, 2011 at 7:55 PM, Ian Holsman had...@holsman.net wrote:
I was wondering if this (and supporting patches?) could be easily applied to
0.74, or if the current
+1
-Chris
On May 30, 2011, at 12:04 PM, Eric Evans wrote:
OK, let's try this yet again; I propose the following artifacts for release
as 0.8.0 (final).
SVN:
https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.8.0@r1129278
Artifacts:
+1
On Mon, Nov 28, 2011 at 10:41 AM, Jonathan Ellis jbel...@gmail.com wrote:
+1
On Fri, Nov 25, 2011 at 6:44 AM, Sylvain Lebresne sylv...@datastax.com
wrote:
So, 1.0.3 was not as solid as one would have hoped and CASSANDRA-3510 is
fairly bad. We've also fixed a few concurrency bugs and
