Build failed in Jenkins: Cassandra-quick #762

See -- [...truncated 400 lines...] [junit] Testsuite: org.apache.cassandra.gms.GossipDigestTest [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.154 sec [junit] [junit] Testsu

Build failed in Jenkins: Cassandra-quick #761

See -- [...truncated 393 lines...] [junit] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.914 sec [junit] [junit]

Build failed in Jenkins: Cassandra-quick #760

See -- [...truncated 408 lines...] [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.607 sec [junit] [junit] Testsuite: org.apache.cassandra.io.BloomFilterTrackerTest [junit] T

Re: Memtable tuning in 1.0 and higher

Hi Jonathan, Looks good, any chance of porting this fix to the 1.0 branch? Kind regards Joost Sent from my iPhone On 1 jul. 2012, at 09:25, Jonathan Ellis wrote: > On Thu, Jun 28, 2012 at 1:39 PM, Joost van de Wijgerd > wrote: >> the currentThoughput is increased even before the data is me

Build failed in Jenkins: Cassandra-quick #759

See -- [...truncated 393 lines...] [junit] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.96 sec [junit] [junit]

Build failed in Jenkins: Cassandra-quick #758

See -- Started by an SCM change Building remotely on ubuntu4 in workspace Checkout:Cassandra-quick /

Re: Memtable tuning in 1.0 and higher

On Thu, Jun 28, 2012 at 1:39 PM, Joost van de Wijgerd wrote: > the currentThoughput is increased even before the data is merged into the > memtable so it is actually measuring the throughput afaik. You're right. I've attached a patch to https://issues.apache.org/jira/browse/CASSANDRA-4399 to fix

Build failed in Jenkins: Cassandra-quick #757

See -- [...truncated 393 lines...] [junit] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.99 sec [junit] [junit]