Re: [VOTE] Release Apache Cassandra 0.7.5

[Eric Evans]

On Fri, 2011-04-22 at 19:17 +0200, Sylvain Lebresne wrote:
> I propose the following artifacts for release as 0.7.5.

+1

> 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/


-- 
Eric Evans
eev...@rackspace.com

Build failed in Jenkins: Cassandra-0.8 #45

[Apache Jenkins Server]

See 

Changes:

[jbellis] add INSERT cql doc section
patch by Pavel Yaskevich for CASSANDRA-2533

--
[...truncated 1984 lines...]
[junit]  WARN 14:15:59,140 Generated random token 
Token(bytes[fbe86299dcaaa351bfa2c0259860fb3a]). 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.123 sec
[junit] 
[junit] Testsuite: 
org.apache.cassandra.dht.CollatingOrderPreservingPartitionerTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.471 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.dht.OrderPreservingPartitionerTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 1.166 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.dht.RandomPartitionerTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.758 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.dht.RangeTest
[junit] Tests run: 13, Failures: 0, Errors: 0, Time elapsed: 0.383 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.gms.ArrivalWindowTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.125 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.gms.GossipDigestTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.057 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.gms.SerializationsTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.392 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.hadoop.ColumnFamilyInputFormatTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.201 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.io.BloomFilterTrackerTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.365 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.io.CompactSerializerTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.76 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.io.LazilyCompactedRowTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 32.505 sec
[junit] 
[junit] - Standard Error -
[junit]  WARN 14:16:32,928 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.058 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.io.sstable.IndexHelperTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.065 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.io.sstable.LegacySSTableTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.44 sec
[junit] 
[junit] - Standard Error -
[junit]  WARN 14:16:56,350 Invalid file '.svn' in data directory 

[junit]  WARN 14:16:56,951 Invalid file '.svn' in data directory 

[junit] -  ---
[junit] Testsuite: org.apache.cassandra.io.sstable.SSTableReaderTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 7.937 sec
[junit] 
[junit] - Standard Error -
[junit]  WARN 14:17:03,744 setting live ratio to maximum of 64 instead of 
{}, newRatio
[junit] -  ---
[junit] Testsuite: org.apache.cassandra.io.sstable.SSTableTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 1.796 sec
[junit] 
[junit] Testsuite: 
org.apache.cassandra.io.sstable.SSTableWriterCommutativeTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.465 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.io.sstable.SSTableWriterTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 1.169 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.io.util.BufferedRandomAccessFileTest
[junit] Tests run: 20, Failures: 0, Errors: 0, Time elapsed: 4.785 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.locator.DynamicEndpointSnitchTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 6.15 sec
[junit] 
[junit] Testsuite: org.apache.cassandra.locator.NetworkTopologyStrategyTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.429 sec
[junit] 
[junit] Testsuite: 
org.apache.cassandra.locator.OldNetworkTopologyStrategyTest
[junit] 

[VOTE RESULTS] Apache Cassandra 0.7.5 release

[Sylvain Lebresne]

On Fri, 2011-04-22 at 19:17 +0200, Sylvain Lebresne 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.

We have 4 binding +1s, plus 1 other and no -1s.  The vote passes.

I'll get everything published.

--
Sylvain

Another beta?

[Eric Evans]

Are we ready for a second beta?  Or, is confidence is high enough for a
release candidate?

-- 
Eric Evans
eev...@rackspace.com

Re: Another beta?

[Jonathan Ellis]

I'd be fine w/ another beta after fixing CASSANDRA-2549.  I think
CASSANDRA-2561 is also ready for review.

I think most of the other 6 issues tagged 0.8.0 [1] should be fixed
before RC.  (Not sure of severity of CASSANDRA-2056 though, and
CASSANDRA-2556 may not be a 0.8 regression, I will check into that
this morning.)

https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+CASSANDRA+AND+fixVersion+%3D+%220.8.0%22+AND+resolution+%3D+Unresolved+ORDER+BY+due+ASC%2C+priority+DESC%2C+created+ASC&mode=hide

On Wed, Apr 27, 2011 at 11:38 AM, Eric Evans  wrote:
>
> Are we ready for a second beta?  Or, is confidence is high enough for a
> release candidate?
>
> --
> Eric Evans
> eev...@rackspace.com
>
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Jenkins build is back to normal : Cassandra-0.8 #46

[Apache Jenkins Server]

See 

Re: hinted handoff should use its own sstables

[Jonathan Ellis]

Sounds like you want https://issues.apache.org/jira/browse/CASSANDRA-2045

On Tue, Apr 26, 2011 at 8:38 AM, Edward Capriolo  wrote:
> 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 :)
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Re: [VOTE] Release Apache Cassandra 0.8.0-beta1 artifacts in Maven Central

[Jonathan Ellis]

+1

On Tue, Apr 26, 2011 at 8:44 AM, Stephen Connolly  wrote:
> 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
>



-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of DataStax, the source for professional Cassandra support
http://www.datastax.com

Re: [VOTE] Release Apache Cassandra 0.8.0-beta1 artifacts in Maven Central

[Eric Evans]

On Tue, 2011-04-26 at 14:44 +0100, Stephen Connolly wrote:
>  * 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 

-1

Why are we making up a different version number for the client code?

-- 
Eric Evans
eev...@rackspace.com

Re: [VOTE] Release Apache Cassandra 0.8.0-beta1 artifacts in Maven Central

[Stephen Connolly]

On 28 April 2011 00:55, Eric Evans  wrote:
> On Tue, 2011-04-26 at 14:44 +0100, Stephen Connolly wrote:
>>  * 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
>
> -1
>
> Why are we making up a different version number for the client code?
>

1. because that version of the driver has a hard dependency on the
other two jars, and because it is still in tree, therefore it is
released in sync.

2. I cannot release another 1.0.0 artifact as you cannot overwrite
versions in maven central.  once you release a version it is released,
so unless 0.8.0-beta2 comes with cql 1.0.1 then we are in trouble. You
will literally have to increment the cql version for _every single
release of the main jars_ or else I will have to make two sets of
build targets one which releases cql only and the other which releases
everything but cql. That is a messy release process to follow, but if
that's what you want...

from my PoV, there will be many issues releasing (oh why is this fix
for cql not in the new release... yes it is... no it isn't... oh,
somebody forgot to increment the cql version when doing the release
and you are using maven central) unless you do one of several options:
  * move cql out of tree (so that it is released on its own
schedule... we do this @maven for everything... many trees with many
independent release schedules)
  * tie the cql version to the main tree version (what I did)
  * make the cql version a combo of the main and the cql version (i.e.
1.0.0-0.8.0-beta1)
  * keep cql in tree but make the build have two targets, 1st for
everything but cql, 2nd for only cql (that will be a mess but it is a
solution)

We can bemoan Maven Central's policy (you can only release a specific
version number once and only once), but that does not solve the issue
that users want dependencies from a Maven repository, and Maven's
architecture will not re-download a release version because of it's
central assumption that releases do not change, so even if you could
re-release a 1.0.0, anyone who used the old 1.0.0 would not get the
new release (this is why -SNAPSHOTs are different from releases, Maven
expects -SNAPSHOTs might change and will check for new versions... but
you cannot put -SNAPSHOTs in a release repository)

-Stephen

> --
> Eric Evans
> eev...@rackspace.com
>
>