Build failed in Jenkins: Cassandra #864
See https://builds.apache.org/hudson/job/Cassandra/864/changes
Changes:
[slebresne] merge CASSANDRA-2557 from trunk
--
[...truncated 2004 lines...]
[junit] Testsuite: org.apache.cassandra.db.context.CounterContextTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.545 sec
[junit]
[junit] Testsuite: org.apache.cassandra.db.marshal.IntegerTypeTest
[junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 0.19 sec
[junit]
[junit] Testsuite: org.apache.cassandra.db.marshal.RoundTripTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 0.421 sec
[junit]
[junit] Testsuite: org.apache.cassandra.db.marshal.TimeUUIDTypeTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.144 sec
[junit]
[junit] Testsuite: org.apache.cassandra.db.marshal.TypeCompareTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.081 sec
[junit]
[junit] Testsuite: org.apache.cassandra.db.marshal.TypeValidationTest
[junit] Tests run: 9, Failures: 0, Errors: 0, Time elapsed: 0.336 sec
[junit]
[junit] Testsuite: org.apache.cassandra.db.marshal.UUIDTypeTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.111 sec
[junit]
[junit] Testsuite: org.apache.cassandra.db.migration.SerializationsTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.643 sec
[junit]
[junit] Testsuite: org.apache.cassandra.dht.BootStrapperTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 2.649 sec
[junit]
[junit] - Standard Error -
[junit] WARN 01:18:39,011 Generated random token
Token(bytes[ca31d741e8acfaade4cf01dd9a0e0cfa]). Random tokens will result in an
unbalanced ring; see http://wiki.apache.org/cassandra/Operations
[junit] - ---
[junit] Testsuite: org.apache.cassandra.dht.ByteOrderedPartitionerTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 1.365 sec
[junit]
[junit] Testsuite:
org.apache.cassandra.dht.CollatingOrderPreservingPartitionerTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.736 sec
[junit]
[junit] Testsuite: org.apache.cassandra.dht.OrderPreservingPartitionerTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1.21 sec
[junit]
[junit] Testsuite: org.apache.cassandra.dht.RandomPartitionerTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.811 sec
[junit]
[junit] Testsuite: org.apache.cassandra.dht.RangeTest
[junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 0.447 sec
[junit]
[junit] Testsuite: org.apache.cassandra.gms.ArrivalWindowTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.137 sec
[junit]
[junit] Testsuite: org.apache.cassandra.gms.GossipDigestTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.069 sec
[junit]
[junit] Testsuite: org.apache.cassandra.gms.SerializationsTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.426 sec
[junit]
[junit] Testsuite: org.apache.cassandra.hadoop.ColumnFamilyInputFormatTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.224 sec
[junit]
[junit] Testsuite: org.apache.cassandra.io.BloomFilterTrackerTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.377 sec
[junit]
[junit] Testsuite: org.apache.cassandra.io.CompactSerializerTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.615 sec
[junit]
[junit] Testsuite: org.apache.cassandra.io.LazilyCompactedRowTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 2.479 sec
[junit]
[junit] - Standard Error -
[junit] WARN 01:19:01,137 setting live ratio to maximum of 64 instead of
{}, newRatio
[junit] - ---
[junit] Testsuite: org.apache.cassandra.io.sstable.DescriptorTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.063 sec
[junit]
[junit] Testsuite: org.apache.cassandra.io.sstable.IndexHelperTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.077 sec
[junit]
[junit] Testsuite: org.apache.cassandra.io.sstable.LegacySSTableTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.569 sec
[junit]
[junit] - Standard Error -
[junit] WARN 01:19:05,135 Invalid file '.svn' in data directory
https://builds.apache.org/hudson/job/Cassandra/ws/cassandra/test/data/legacy-sstables/b/Keyspace1.
[junit] WARN 01:19:05,817 Invalid file '.svn' in data directory
https://builds.apache.org/hudson/job/Cassandra/ws/cassandra/test/data/legacy-sstables/e/Keyspace1.
[junit] - ---
[junit] Testsuite:
hinted handoff should use its own sstables
So maybe this idea has been sent around before but I would like to know what everyone thinks. We have a huge column family called bigdata let's say 200 gb a node. We have used cass* as you would expect we never read before writing and during our bulk loading we can get rates like 2000 inserts per second per node. This morning I noticed this cf on only some nodes had a lot of reads which went on for hours. Since our apps should not have been reading I dove in. What was happening was a node was down during the bulk load period. As a resukt when it came alive the other node with hints went to deliver them. The problem was the other node was high io trying to deliver hints. I see why. Cassandra does NOT write before read EXCEPT when writing a handoff. This is not a good thing. It means the bigger big data cf gets the more intensive delivering the hint will be on the sender side. Write rate may be 2000 but they can not be read that fast. I know you can now drop and throttle hh in 0.7.0 but this is not good enough since this only takes longer to get consistent. Or you never get consistent so here is my thinking... Store hints in separate physical files and or possibly deliver those file by streaming. Maybe there is already a jira out there on this. I just work up so to me it is an original idea :)
Re: [VOTE] Release Apache Cassandra 0.7.5
+1 On Fri, Apr 22, 2011 at 12:17, Sylvain Lebresne slebre...@apache.org wrote: I propose the following artifacts for release as 0.7.5. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-113/org/apache/cassandra/apache-cassandra/0.7.5/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-113 The artifacts as well as a debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours. [1]: goo.gl/1i0Ce (CHANGES.txt) [2]: goo.gl/cLaqR (NEWS.txt)
[VOTE] Release Apache Cassandra 0.8.0-beta1 artifacts in Maven Central
Per the Apache release rules, only artifacts which have been voted on can be released. Thus, as I missed the main release vote, I cannot tag onto the end. The artifacts I want to release are: https://repository.apache.org/content/repositories/orgapachecassandra-114/ Notes: * The tar.gz files are different from the main as the -src.tar.gz includes my patch and the -bin.tar.gz has different timestamps on the javadocs (previously I had just been reusing eric's tar.gz's and hacking the patch to no overwrite them... but I think it is better to have the actual source of what is used to generate all the artifacts that make up this staging repo) * I have given the CQL driver jar the same version number as everything else, because it is only going to work with the 0.8.0-beta1 jars anyway. Please vote (see http://www.apache.org/foundation/voting.html#ReleaseVotes) +1: Go ahead and release it 0: I have some issues with the release -1: I have something I think merits re-spinning this release Vote will be open for 72 hours unless the PMC says we can finish quicker and we have met the 3 or more binding +1's minimum -Stephen P.S. I do not have a binding vote at Cassandra, but here is my +1 anyway
Re: [VOTE] Release Apache Cassandra 0.7.5
I've spotted a minor issue with my CASSANDRA-1851 patch... I'll raise a JIRA to address, and I will have to attach a staging repository to this vote for it to be closed successfully (i.e. we are missing the cassandra-parent pom that all the 0.7.5 poms inherit from) On 22 April 2011 18:17, Sylvain Lebresne slebre...@apache.org wrote: I propose the following artifacts for release as 0.7.5. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-113/org/apache/cassandra/apache-cassandra/0.7.5/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-113 The artifacts as well as a debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours. [1]: goo.gl/1i0Ce (CHANGES.txt) [2]: goo.gl/cLaqR (NEWS.txt)
Re: [VOTE] Release Apache Cassandra 0.7.5
https://repository.apache.org/content/repositories/orgapachecassandra-115/ contains the missing artifact for deployment to maven central https://issues.apache.org/jira/browse/CASSANDRA-2562 will patch 0.7.x to ensure this works going forward. Unless anyone objects, please consider the 115 staging repo as appended onto this vote -Stephen On 26 April 2011 14:45, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I've spotted a minor issue with my CASSANDRA-1851 patch... I'll raise a JIRA to address, and I will have to attach a staging repository to this vote for it to be closed successfully (i.e. we are missing the cassandra-parent pom that all the 0.7.5 poms inherit from) On 22 April 2011 18:17, Sylvain Lebresne slebre...@apache.org wrote: I propose the following artifacts for release as 0.7.5. SVN: https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.7@r1095960 Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-113/org/apache/cassandra/apache-cassandra/0.7.5/ Staging repository: https://repository.apache.org/content/repositories/orgapachecassandra-113 The artifacts as well as a debian package are also available here: http://people.apache.org/~slebresne/ The vote will be open for 72 hours. [1]: goo.gl/1i0Ce (CHANGES.txt) [2]: goo.gl/cLaqR (NEWS.txt)
Jenkins build is back to normal : Cassandra #865
See https://builds.apache.org/hudson/job/Cassandra/865/changes
Re: Why is the CQL jar versioned independently?
so will cql get its own tree from which releases well be cut, or will it get released always at the same time? - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 26 Apr 2011 22:19, Eric Evans eev...@rackspace.com wrote: On Tue, 2011-04-26 at 13:31 +0100, Stephen Connolly wrote: From what I can see, the intent is to always release lock-step in sync with cassandra, in which case the version number should be the cassandra version number... unless you are implying that this is CQL version 1.0.0 and there may be a future time when you could have CQL version 2.0.0 with a different incompatible syntax... CQL client versioning does *not* move in lock-step with either Cassandra or the CQL specification (though if you adhere to semver.org for both the spec and the library then *major* versions will effectively move in lock-step). -- Eric Evans eev...@rackspace.com
Re: Why is the CQL jar versioned independently?
On Tue, 2011-04-26 at 22:42 +0100, Stephen Connolly wrote: so will cql get its own tree from which releases well be cut, or will it get released always at the same time? It would probably make sense at some point to separate the build for the Java client code so that releases could be made independently. But, even if the releases continue to occur only when Cassandra does, the version numbers need to move independently. -- Eric Evans eev...@rackspace.com
Jenkins build is back to stable : Cassandra-Coverage #36
See https://builds.apache.org/hudson/job/Cassandra-Coverage/36/changes
