Build failed in Jenkins: Cassandra-quick #726

2012-06-28 Thread Apache Jenkins Server
See -- [...truncated 387 lines...] [junit] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.908 sec [junit] [junit]

Build failed in Jenkins: Cassandra-quick #725

2012-06-28 Thread Apache Jenkins Server
See -- [...truncated 388 lines...] [junit] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.942 sec [junit] [junit]

Build failed in Jenkins: Cassandra-quick #724

2012-06-28 Thread Apache Jenkins Server
See -- [...truncated 381 lines...] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.9 sec [junit] [junit] Testsuite: org

Build failed in Jenkins: Cassandra #1619

2012-06-28 Thread Apache Jenkins Server
See -- Started by an SCM change Building remotely on ubuntu4 in workspace Checkout:Cassandra / - hudson.remoting.Cha

Build failed in Jenkins: Cassandra #1618

2012-06-28 Thread Apache Jenkins Server
See -- Started by an SCM change Building remotely on ubuntu4 in workspace Checkout:Cassandra / - hudson.remoting.Cha

Build failed in Jenkins: Cassandra-quick #723

2012-06-28 Thread Apache Jenkins Server
See Changes: [jbellis] commitlog cleanup; fixes stderr for RecoveryManager2Test on Windows -- [...truncated 382 lines...] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Test

Build failed in Jenkins: Cassandra #1617

2012-06-28 Thread Apache Jenkins Server
See -- Started by an SCM change Building remotely on ubuntu4 in workspace Checkout:Cassandra / - hudson.remoting.Cha

Build failed in Jenkins: Cassandra-quick #722

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

Build failed in Jenkins: Cassandra-quick #721

2012-06-28 Thread Apache Jenkins Server
See -- [...truncated 427 lines...] [junit] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.933 sec [junit] [junit]

Build failed in Jenkins: Cassandra-quick #720

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

Build failed in Jenkins: Cassandra-quick #719

2012-06-28 Thread Apache Jenkins Server
See Changes: [vijay2win] Add Commitlog Versioning [vijay2win] Fix License headers and add assert which was missed. -- [...truncated 381 lines...] [junit] Testsuite: org.apache.cassandra.dht.R

Build failed in Jenkins: Cassandra-quick #718

2012-06-28 Thread Apache Jenkins Server
See Changes: [eevans] lookup hints by ID, not token -- [...truncated 381 lines...] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time

Build failed in Jenkins: Cassandra-quick #717

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

Build failed in Jenkins: Cassandra-quick #716

2012-06-28 Thread Apache Jenkins Server
See -- [...truncated 381 lines...] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.906 sec [junit] [junit] Testsuite: o

Build failed in Jenkins: Cassandra-quick #715

2012-06-28 Thread Apache Jenkins Server
See -- [...truncated 387 lines...] [junit] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.931 sec [junit] [junit]

Re: Memtable tuning in 1.0 and higher

2012-06-28 Thread Joost van de Wijgerd
Hi Jonathan, The problem is not that I haven't allocated enough memory to the memtables, the problem is that the memtable for this particular CF flushes too early because the liveRation stays at 1.0. When looking at the code it seems to me the the liveRatio is calculated based on the throughput of

Build failed in Jenkins: Cassandra-quick #714

2012-06-28 Thread Apache Jenkins Server
See -- [...truncated 381 lines...] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.907 sec [junit] [junit] Testsuite: o

Re: Memtable tuning in 1.0 and higher

2012-06-28 Thread Jonathan Ellis
[moving to user list] 1.0 doesn't care about throughput or op count anymore, only whether the total memory used by the *currrent* data in the memtables has reached the global limit. So, it automatically doesn't count "historical" data that's been overwritten in the current memtable. So, you may

Re: Distinct with Cql

2012-06-28 Thread Jonathan Ellis
No. (Moving to user list.) On Jun 28, 2012 8:17 AM, "Fábio Caldas" wrote: > It´s possible to use distinct on cql? > > -- > Atenciosamente, > Fábio Caldas >

Build failed in Jenkins: Cassandra-quick #713

2012-06-28 Thread Apache Jenkins Server
See -- [...truncated 382 lines...] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.674 sec [junit] [junit] Testsuite: o

Distinct with Cql

2012-06-28 Thread Fábio Caldas
It´s possible to use distinct on cql? -- Atenciosamente, Fábio Caldas

Build failed in Jenkins: Cassandra-quick #712

2012-06-28 Thread Apache Jenkins Server
See Changes: [xedin] (cql3) allow updating column_alias types -- [...truncated 381 lines...] [junit] Testsuite: org.apache.cassandra.dht.RangeTest [junit] Tests run: 22, Failures: 0, Error

Build failed in Jenkins: Cassandra #1612

2012-06-28 Thread Apache Jenkins Server
See -- Started by an SCM change Building remotely on ubuntu4 in workspace Checkout:Cassandra / - hudson.remoting.Cha

Build failed in Jenkins: Cassandra-quick #711

2012-06-28 Thread Apache Jenkins Server
See Changes: [sylvain] Fix leveled promote integrity check -- [...truncated 382 lines...] [junit] Tests run: 22, Failures: 0, Errors: 0, Time elapsed: 0.673 sec [junit] [junit] Testsu

Memtable tuning in 1.0 and higher

2012-06-28 Thread Joost van de Wijgerd
Hi, I work for eBuddy, We've been using Cassandra in production since 0.6 (using 0.7 and 1.0, skipped 0.8) and use it for several Use Cases. One of our uses is to persist our sessions. Some background, in our case sessions are long lived, we have a mobile messaging platform where sessions are ess