Re: Commit log changes in 0.7

2010-02-26 Thread Ryan King
On Fri, Feb 26, 2010 at 9:22 AM, Gary Dusbabek gdusba...@gmail.com wrote: The commit log currently has a header section whose size is constant, but is a function of the total number of defined column families. This isn't going to work with CASSANDRA-44 where CFs can be added or removed on the

Re: [VOTE] Release 0.6.0-beta2

2010-02-23 Thread Ryan King
+1 On Tue, Feb 23, 2010 at 12:03 PM, Gary Dusbabek gdusba...@gmail.com wrote: +1 On Tue, Feb 23, 2010 at 13:36, Eric Evans eev...@rackspace.com wrote: There has been a lot of cool work done since our last release[1] (0.5.0), and while there's still a bit more to be done[2], the dust is

Re: thinking about dropping hinted handoff

2010-02-22 Thread Ryan King
On Wed, Jan 27, 2010 at 12:02 PM, Ryan King r...@twitter.com wrote: On Wed, Jan 27, 2010 at 11:49 AM, Jonathan Ellis jbel...@gmail.com wrote: On Wed, Jan 27, 2010 at 1:48 PM, Stu Hood stu.h...@rackspace.com wrote: The HH code currently tries to send the hints to nodes other than the natural

Re: thinking about dropping hinted handoff

2010-02-22 Thread Ryan King
2010/2/22 Peter Schüller sc...@spotify.com: #3 is, I think, the right answer. It make our system simpler and it makes the behavior in failure conditions more predictable and safe. Any thoughts on time-to-self-heal? My impression browsing the code, and it seems to be confirmed by some wiki

Re: thinking about dropping hinted handoff

2010-02-22 Thread Ryan King
On Mon, Feb 22, 2010 at 2:05 PM, Jonathan Ellis jbel...@gmail.com wrote: On Mon, Feb 22, 2010 at 1:53 PM, Ryan King r...@twitter.com wrote: So, after having some more experience with HH, I've reformed my opinion. I think we have 3 options: 1. Make the natural endpoints responsible

Re: thinking about dropping hinted handoff

2010-02-22 Thread Ryan King
On Mon, Feb 22, 2010 at 5:01 PM, Jonathan Ellis jbel...@gmail.com wrote: On Mon, Feb 22, 2010 at 6:57 PM, Ryan King r...@twitter.com wrote: I think I find it more compelling because we're currently experiencing pain related to HH. I'd be ok with keeping it as long as we can make the effects

Re: 0.6, 0.7, and the future

2010-02-17 Thread Ryan King
On Wed, Feb 17, 2010 at 1:32 PM, Jonathan Ellis jbel...@gmail.com wrote: We're looking at branching 0.6 today and starting 0.7 work. 0.6 shaped up to be a really nice follow-up to 0.5, where we improved just about everything while keeping the upgrade path super easy.  (We changed the network

Re: thinking about dropping hinted handoff

2010-01-27 Thread Ryan King
On Wed, Jan 27, 2010 at 8:34 AM, Jonathan Ellis jbel...@gmail.com wrote: While being able to write (with CL.ZERO or new-in-0.6 ANY) even if all the real write targets are down is cool, but since your goal in real life is to keep enough replicas alive that you can actually do reads, I'm not

Re: thinking about dropping hinted handoff

2010-01-27 Thread Ryan King
On Wed, Jan 27, 2010 at 11:49 AM, Jonathan Ellis jbel...@gmail.com wrote: On Wed, Jan 27, 2010 at 1:48 PM, Stu Hood stu.h...@rackspace.com wrote: The HH code currently tries to send the hints to nodes other than the natural endpoints. If small-scale performance is a problem, we could make the

Re: [VOTE] Release 0.5.0 (final)

2010-01-18 Thread Ryan King
+1 On Mon, Jan 18, 2010 at 1:13 PM, Gary Dusbabek gdusba...@gmail.com wrote: +1 On Mon, Jan 18, 2010 at 14:28, Eric Evans eev...@rackspace.com wrote: I propose the following tag and artifacts for 0.5.0: SVN Tag: https://svn.apache.org/repos/asf/incubator/cassandra/tags/cassandra-0.5.0

Re: release policy

2010-01-11 Thread Ryan King
On Fri, Jan 8, 2010 at 11:47 AM, Jonathan Ellis jbel...@gmail.com wrote: I think we have enough people using Cassandra in production now that it would be useful to be explicit about the kinds of changes we will make between major and minor releases.  Here is one possibility: Minor releases

Re: release policy

2010-01-11 Thread Ryan King
On Mon, Jan 11, 2010 at 10:15 AM, Jonathan Ellis jbel...@gmail.com wrote: On Mon, Jan 11, 2010 at 12:03 PM, Ryan King r...@twitter.com wrote: Both of the above are fine. I think we could even tolerate having to run an upgrade tool with a node, as long as we can do it one at a time and as long

Re: Cassandra users survey

2009-11-20 Thread Ryan King
At twitter we're working on using Cassandra to replace our currents storage for all tweets. We have a cluster in production that's being populated outside the the user-critical path (ie, the cassandra writing is async). Additionally, we're testing and evaluating for basically everything else in

Re: [VOTE] Website

2009-11-11 Thread Ryan King
Looks great. +1 -ryan On Wed, Nov 11, 2009 at 2:22 PM, Johan Oskarsson jo...@oskarsson.nu wrote: +1. A great step forward from the current version and a good base to improve upon. /Johan Eric Evans wrote: The current website is quite ugly, and I don't know about you, but I'm itching to

Re: [VOTE] Change data model names for 0.5

2009-08-24 Thread Ryan King
+1 On Mon, Aug 24, 2009 at 12:29 PM, Evan Weaverewea...@gmail.com wrote: Resolved, that the data model names should be changed in Cassandra 0.5. Evan PS. Committers have the most weight, but everyone's voice is heard. -- Evan Weaver