Build failed in Jenkins: Cassandra-Coverage #290

2012-08-24 Thread Apache Jenkins Server
See -- Started by an SCM change Building remotely on ubuntu4 in workspace Checkout:Cassandra-Coverage /

Build failed in Jenkins: Cassandra-quick #1168

2012-08-24 Thread Apache Jenkins Server
See Changes: [jbellis] add src/java/org/apache/cassandra/db/BlacklistedDirectories.java [jbellis] finish renaming DFMode -> DFPolicy [jbellis] add DMP.ignore to avoid surprises when upgrading w/ old config file --

Re: Upgrade path for virtual nodes

2012-08-24 Thread Eric Evans
On Fri, Aug 24, 2012 at 11:27 AM, Jonathan Ellis wrote: > On Fri, Aug 24, 2012 at 11:23 AM, Eric Evans wrote: >> Actually, now that I think about it, I'd probably drop the entire >> notion of a "coordinator", and write the respective entiries into a >> column family in the system keyspaces. Each

Build failed in Jenkins: Cassandra-quick #1167

2012-08-24 Thread Apache Jenkins Server
See -- Started by an SCM change Building remotely on ubuntu4 in workspace Checkout:Cassandra-quick /

Build failed in Jenkins: Cassandra #1970

2012-08-24 Thread Apache Jenkins Server
See Changes: [jbellis] add disk_failure_policy -- Started by an SCM change Building remotely on ubuntu1 in workspace Checkout:Cassandra /

Build failed in Jenkins: Cassandra-quick #1166

2012-08-24 Thread Apache Jenkins Server
See Changes: [jbellis] add disk_failure_policy -- Started by an SCM change Building remotely on ubuntu1 in workspace Checkout:Cassandra-quick

Re: Upgrade path for virtual nodes

2012-08-24 Thread Jonathan Ellis
On Fri, Aug 24, 2012 at 11:23 AM, Eric Evans wrote: > Actually, now that I think about it, I'd probably drop the entire > notion of a "coordinator", and write the respective entiries into a > column family in the system keyspaces. Each system could then work > through their respective queue of re

Re: Upgrade path for virtual nodes

2012-08-24 Thread Eric Evans
On Tue, Aug 21, 2012 at 2:54 PM, Jonathan Ellis wrote: > On Mon, Aug 20, 2012 at 4:55 PM, Eric Evans wrote: >> Shuffling the ranges to create a random distribution from contiguous >> ranges has the potential to move a *lot* of data around (all of it, >> basically). Doing this in an optimal way w

Build failed in Jenkins: Cassandra-quick #1165

2012-08-24 Thread Apache Jenkins Server
See -- [...truncated 400 lines...] [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 8.589 sec [junit] [junit] Testsuite: org.apache.cassandra.io.CompactSerializerTest [junit] T