Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-07 Thread Jason Brown
+1 On Thu, Apr 7, 2016 at 5:17 PM, Aleksey Yeschenko wrote: > +1 > > -- > AY > > On 7 April 2016 at 23:11:17, Jake Luciani (j...@apache.org) wrote: > > I propose the following artifacts for release as 3.0.5. > > sha1: c6e6fa94d28c0d23a8154e3743c05b355dba710a > Git: > > http://git-wip-us.apache.o

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-07 Thread Jonathan Ellis
Tomorrow should be fine. Thanks! On Thu, Apr 7, 2016 at 7:45 PM, Pavel Yaskevich wrote: > So it looks like that changes in CASSANDRA-11383 caused the problem, but we > have a non-intrusive solution for it and we should be able to make > it work by tomorrow, if you still think it is too late for

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-07 Thread Pavel Yaskevich
So it looks like that changes in CASSANDRA-11383 caused the problem, but we have a non-intrusive solution for it and we should be able to make it work by tomorrow, if you still think it is too late for 3.5 we can revert but it would be better to have 3.5 CASSANDRA-11383 + CASSANDRA-11525. On Thu,

Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-07 Thread Aleksey Yeschenko
+1 --  AY On 7 April 2016 at 23:11:17, Jake Luciani (j...@apache.org) wrote: I propose the following artifacts for release as 3.0.5. sha1: c6e6fa94d28c0d23a8154e3743c05b355dba710a Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.5-tentative Artifac

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-07 Thread Pavel Yaskevich
Ok, I will let you know if that's actually is a problem and if so we'll revert it from 3.5. On Thu, Apr 7, 2016 at 3:46 PM, Jonathan Ellis wrote: > I'd recommend then that we revert the OOM fix, release 3.5 on-schedule-ish, > and release an updated fix in 3.6. > > On Thu, Apr 7, 2016 at 5:42 PM,

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-07 Thread Jonathan Ellis
I'd recommend then that we revert the OOM fix, release 3.5 on-schedule-ish, and release an updated fix in 3.6. On Thu, Apr 7, 2016 at 5:42 PM, Pavel Yaskevich wrote: > Yes, it's a new regression because, so far, it looks like it's a result of > us fixing OOM problem discovered in 3.4. > > On Thu

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-07 Thread Pavel Yaskevich
Yes, it's a new regression because, so far, it looks like it's a result of us fixing OOM problem discovered in 3.4. On Thu, Apr 7, 2016 at 3:35 PM, Jonathan Ellis wrote: > So it's a new regression, not present in 3.4? > > On Thu, Apr 7, 2016 at 5:24 PM, Pavel Yaskevich wrote: > > > There is a b

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-07 Thread Jonathan Ellis
So it's a new regression, not present in 3.4? On Thu, Apr 7, 2016 at 5:24 PM, Pavel Yaskevich wrote: > There is a bug in SASI indexes we have introduced in 3.5 - CASSANDRA-11525, > I'm not sure if we want to postpone release until we work it out. > > On Thu, Apr 7, 2016 at 3:19 PM, Brandon Willi

Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-07 Thread Jonathan Ellis
+1 On Thu, Apr 7, 2016 at 5:10 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.0.5. > > sha1: c6e6fa94d28c0d23a8154e3743c05b355dba710a > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.5-tentative > Artifacts: > > https://re

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-07 Thread Pavel Yaskevich
There is a bug in SASI indexes we have introduced in 3.5 - CASSANDRA-11525, I'm not sure if we want to postpone release until we work it out. On Thu, Apr 7, 2016 at 3:19 PM, Brandon Williams wrote: > +1 > > On Thu, Apr 7, 2016 at 5:19 PM, Jake Luciani wrote: > > > I propose the following artifa

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-07 Thread Brandon Williams
+1 On Thu, Apr 7, 2016 at 5:19 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.5. > > sha1: 89bd93502ac141f8cd13f8738bb4314488db2a5a > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.5-tentative > Artifacts: > > https://reposi

[VOTE] Release Apache Cassandra 3.5

2016-04-07 Thread Jake Luciani
I propose the following artifacts for release as 3.5. sha1: 89bd93502ac141f8cd13f8738bb4314488db2a5a Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.5-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1105/org/apache/cas

Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-07 Thread Brandon Williams
+1 On Thu, Apr 7, 2016 at 5:10 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.0.5. > > sha1: c6e6fa94d28c0d23a8154e3743c05b355dba710a > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.5-tentative > Artifacts: > > https://re

[VOTE] Release Apache Cassandra 3.0.5

2016-04-07 Thread Jake Luciani
I propose the following artifacts for release as 3.0.5. sha1: c6e6fa94d28c0d23a8154e3743c05b355dba710a Git: http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.5-tentative Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1104/org/apache

Re: Issue with this mornings upgrade of Staging DataStax Enterprise

2016-04-07 Thread Michael Shuler
This mailing list is for discussing the development of Apache Cassandra. Either talk to your support folks at DataStax or try the user@ list for help installing (which is probably also inappropriate for DSE). FWIW, this is a simple user issue with multiple versions of the same software in apt repo

Issue with this mornings upgrade of Staging DataStax Enterprise

2016-04-07 Thread Ken Schell
Jeff, When you get in this morning can you come by and see me. I tried to upgrade node 01 in staging 10.10.160.42 and received the following issue. I’m going ahead and opening a DataStax Support ticket and see what they suggest. From my screen: root@stga-cass01:/var/log/cassandra# apt-get inst