Re: Cassandra has moved to Git

2012-01-09 Thread Eric Evans
On Mon, Jan 9, 2012 at 9:41 AM, Sylvain Lebresne wrote: >> The other side of the equation is that there is tremendous power to be had >> from distributed versioning, and this proposed workflow discourages taking >> advantage of that > > Would you mind elaborating, maybe be a little more concrete o

Re: Cassandra has moved to Git

2012-01-09 Thread paul cannon
On Mon, Jan 9, 2012 at 10:02 AM, Peter Schuller wrote: > [speaking obviously as non-committer, just offering a perspective] > > A potential factor to consider: If one knows that all work in topic > branches end up merged without anyone first rebasing to clean up, you > now have a constant trade-o

Re: Cassandra has moved to Git

2012-01-09 Thread Peter Schuller
[speaking obviously as non-committer, just offering a perspective] A potential factor to consider: If one knows that all work in topic branches end up merged without anyone first rebasing to clean up, you now have a constant trade-off between history readability and committing often. I personally

Re: Cassandra has moved to Git

2012-01-09 Thread Sylvain Lebresne
Ok, I'll need to stop using Gmail. In the meantime, sorry for the inconvenience, retrying, hoping that Gmail won't randomly screw up the formatting this time. So, I do don't like history that look like the following: > commit : last nits from reviewer > commit : oops, typo that prevented

Re: Cassandra has moved to Git

2012-01-09 Thread Sylvain Lebresne
So, I do don't like history that look like the following: > commit : last nits from reviewer> commit : oops, typo that prevented > compilation> commit : some more fix found during review> commit : > refactor half of preceding patch following reviewer comments> commit : Do > s

Re: Using quorum to read data

2012-01-09 Thread Peter Schuller
> 2012-01-09 11:58:33,325 WARN > [me.prettyprint.cassandra.connection.CassandraHostRetryService] - 192.168.80.31(192.168.80.31):9160 host still appears to be down: Unable to > open transport to 192.168.80.31(192.168.80.31):9160 , > java.net.ConnectException: Connection refused: connect> > > What a

Using quorum to read data

2012-01-09 Thread Michael Vaknine
Hi, I have a 4 node cluster 1.0.3 with replication_factor = 3. QUORUM: Returns the record with the most recent timestamp once a quorum (51%+) of replicas has responded. It also triggers a read repair I am using QUORUM to read and write data so I assume that if I get response from 3 servers