Build failed in Jenkins: Cassandra #1181

See Changes: [jbellis] merge from 1.0 -- [...truncated 2194 lines...] [junit] [junit] [junit] Test org.apache.cassandra.locator.DynamicEndpointSnitchTest FAILED [junit] Testsuite: org

Build failed in Jenkins: Cassandra-quick #90

See Changes: [jbellis] merge from 1.0 -- [...truncated 1545 lines...] [junit] at org.apache.cassandra.service.StorageService.initClient(StorageService.java:367) [junit] at org.apa

Build failed in Jenkins: Cassandra #1180

See Changes: [jbellis] renaming [jbellis] cleanup and fixes for index debug logging -- [...truncated 2213 lines...] [junit] [junit] [junit] Test org.apache.cassandra.locator.DynamicEndpo

Build failed in Jenkins: Cassandra-quick #89

See Changes: [jbellis] renaming [jbellis] cleanup and fixes for index debug logging -- [...truncated 1545 lines...] [junit] at org.apache.cassandra.service.StorageService.initClient(Stora

Build failed in Jenkins: Cassandra #1179

See Changes: [jbellis] merge from 1.0 -- [...truncated 2194 lines...] [junit] [junit] [junit] Test org.apache.cassandra.locator.DynamicEndpointSnitchTest FAILED [junit] Testsuite: org

Build failed in Jenkins: Cassandra-quick #88

See Changes: [jbellis] merge from 1.0 -- [...truncated 1546 lines...] [junit] at org.apache.cassandra.service.StorageService.initClient(StorageService.java:367) [junit] at org.apa

Jenkins build is still unstable: Cassandra-Coverage #156

See

Build failed in Jenkins: Cassandra #1178

See Changes: [xedin] merge from 1.0 -- [...truncated 2114 lines...] [junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.724 sec [junit] [junit] Testsuite: org.apache.cassandra.dh

Build failed in Jenkins: Cassandra-quick #87

See Changes: [xedin] merge from 1.0 -- [...truncated 1446 lines...] [junit] [junit] Testsuite: org.apache.cassandra.db.migration.SerializationsTest [junit] Tests run: 1, Failures: 0, E

Checksumming

how does checksumming in Cassandra work? If there is a bit rot it is detected but how is it fixed? let's say a key column has been corrupted and the corruption is detected. How is it fixed?

Re: Faster byte[] comparisons

Interesting. I've created https://issues.apache.org/jira/browse/CASSANDRA-3434 to have a look at it. -- Sylvain On Mon, Oct 31, 2011 at 6:28 PM, Jason Rutherglen wrote: > "...benchmarks show it as being 2x more CPU-efficient than the > equivalent pure-Java implementation..." > > https://issues.a

Re: [VOTE] Release Apache Cassandra 0.7.10

Including my own vote I'm count 3 binding +1's and no -1's. The vote passes. I'll get the artifacts published. -- Sylvain On Fri, Oct 28, 2011 at 8:23 PM, Jonathan Ellis wrote: > +1 > > On Fri, Oct 28, 2011 at 12:47 PM, Brandon Williams wrote: >> +1 >> On Oct 28, 2011 12:45 PM, "Sylvain Lebresn

Faster byte[] comparisons

"...benchmarks show it as being 2x more CPU-efficient than the equivalent pure-Java implementation..." https://issues.apache.org/jira/browse/HADOOP-7761

Build failed in Jenkins: Cassandra #1177

See Changes: [xedin] merge from 1.0 [jbellis] r/m assert that is causing test problems (see #3116, #3399) [xedin] merge from 1.0 [jbellis] replace compactionlock use in schema migration by checking CFS.isInvalidD patch by jbellis; reviewe

Build failed in Jenkins: Cassandra-quick #86

See Changes: [xedin] merge from 1.0 -- [...truncated 1544 lines...] [junit] at org.apache.cassandra.service.StorageService.initClient(StorageService.java:367) [junit] at org.apach

Build failed in Jenkins: Cassandra-quick #85

See Changes: [jbellis] r/m assert that is causing test problems (see #3116, #3399) [xedin] merge from 1.0 -- [...truncated 1544 lines...] [junit] at org.apache.cassandra.service.StorageSe

Build failed in Jenkins: Cassandra-quick #84

See Changes: [jbellis] replace compactionlock use in schema migration by checking CFS.isInvalidD patch by jbellis; reviewed by slebresne for CASSANDRA-3116 -- [...truncated 1651 lines...] [jun

Re: cassandra.yaml mysteries :-)

On Mon, Oct 31, 2011 at 4:36 PM, Kyle Quest wrote: > Thanks explanation Sylvain!  If we are talking about generic then it > should be Map. This way you don't restrict the data > type and you let the yaml lib parse the data. With Map > my version of SimpleSeedProvider has these kind of configs with

Re: Alternative seed providers

Dynamically generating static node config files is definitely a good solution though it has its limitations too :-) Do you know what kind of pluggable seeds they have at Netflix? On Sun, Oct 30, 2011 at 10:20 PM, Edward Capriolo wrote: > On Sun, Oct 30, 2011 at 11:27 PM, Kyle Quest wrote: > >> I

Re: cassandra.yaml mysteries :-)

Thanks explanation Sylvain! If we are talking about generic then it should be Map. This way you don't restrict the data type and you let the yaml lib parse the data. With Map my version of SimpleSeedProvider has these kind of configs without doing extra text parsing: version a: seed_provider:

Re: [VOTE] Release Apache Cassandra 1.0.1

Including my own vote, I count 3 binding +1's and no -1's. The vote passes. I'll get the artifacts published. -- Sylvain On Sat, Oct 29, 2011 at 2:00 AM, Eric Evans wrote: > On Fri, Oct 28, 2011 at 4:43 AM, Sylvain Lebresne > wrote: >> Since the final release of 1.0.0, we've fixed quite a few

Re: cassandra.yaml mysteries :-)

Because a seed_provider can be custom, you can write your own. The only one we ship by default is the SimpleSeedProvided, but you can create your own that say, query some service over the network to get the list of seeds. So the parameters have to be generic for that to work and having the paramete