Build failed in Jenkins: Cassandra-quick #1126

See -- [...truncated 387 lines...] [junit] [junit] Testsuite: org.apache.cassandra.io.BloomFilterTrackerTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 5.601 sec [junit]

Build failed in Jenkins: Cassandra-quick #1127

See -- [...truncated 388 lines...] [junit] Testsuite: org.apache.cassandra.io.BloomFilterTrackerTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 5.185 sec [junit] [junit]

Build failed in Jenkins: Cassandra-quick #1128

See -- [...truncated 387 lines...] [junit] [junit] Testsuite: org.apache.cassandra.io.BloomFilterTrackerTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 5.561 sec [junit]

Build failed in Jenkins: Cassandra-quick #1129

See -- [...truncated 388 lines...] [junit] [junit] Testsuite: org.apache.cassandra.io.BloomFilterTrackerTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 5.611 sec [junit]

Problem while configuring key and row cache?

I started exploring apache cassandra 1.1.3. I am facing problem with how to improve performance of cassandra using caching configurations. I tried setting following configurations: ./nodetool -h 107.108.189.204 setcachecapacity DemoUser Users 25 0 ./nodetool -h 107.108.189.204 setcachecapacity

Re: Problem while configuring key and row cache?

setcachecapacity is obsolete in 1.1+. Looks like we missed removing it from nodetool. See http://www.datastax.com/dev/blog/caching-in-cassandra-1-1 for background. (Moving to users@.) On Tue, Aug 21, 2012 at 8:19 AM, Amit Handa wrote: > I started exploring apache cassandra 1.1.3. I am facing p

Build failed in Jenkins: Cassandra-quick #1130

See Changes: [jbellis] upgradesstables recommended for #4436 -- [...truncated 396 lines...] [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 24.418 sec [junit] [junit] Tes

Build failed in Jenkins: Cassandra #1954

See -- Started by an SCM change Building remotely on ubuntu4 in workspace Checkout:Cassandra / - hudson.remoting.Cha

Build failed in Jenkins: Cassandra-quick #1131

See -- [...truncated 396 lines...] [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 13.286 sec [junit] [junit] Testsuite: org.apache.cassandra.io.CompactSerializerTest [junit]

Re: Upgrade path for virtual nodes

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 would mean never moving a > range more than once. Since it is

Build failed in Jenkins: Cassandra-quick #1132

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

Build failed in Jenkins: Cassandra-quick #1133

See Changes: [xedin] add Murmur3Partitioner and make it default for new installations -- [...truncated 390 lines...] [junit] [junit] Testsuite: org.apache.cassandra.io.CompactSerializerT

Build failed in Jenkins: Cassandra-quick #1134

See -- [...truncated 387 lines...] [junit] [junit] Testsuite: org.apache.cassandra.io.BloomFilterTrackerTest [junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 5.371 sec [junit]

Build failed in Jenkins: Cassandra-Coverage #287

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

Build failed in Jenkins: Cassandra-quick #1135

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

Build failed in Jenkins: Cassandra-quick #1136

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

Build failed in Jenkins: Cassandra-quick #1137

See Changes: [dbrosius] remove dead assignment -- [...truncated 393 lines...] [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.222 sec [junit] [junit] Testsuite: org.apa

Re: Problem while configuring key and row cache?

Hi, Thanks Jonathan for your reply. I modified key_cache_size_in_mb and row_cache_size_in_mb values inside cassandra.yaml. but not able to see it's effect using command " *./nodetool -h 107.108.189.212 cfstats*". Can u let me know how to verify that the setting for key_cache_size and row_chache_si