Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-08 Thread Benjamin Lerer 
+1

On Fri, Apr 8, 2016 at 12:10 AM, 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://repository.apache.org/content/repositories/orgapachecassandra-1104/org/apache/cassandra/apache-cassandra/3.0.5/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1104/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/f2b0Di (CHANGES.txt)
> [2]: http://goo.gl/bHIeYj (NEWS.txt)
> [3]: https://goo.gl/noLkHT (DataStax Test Report)
>

Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-08 Thread Sylvain Lebresne 
+1

On Fri, Apr 8, 2016 at 9:24 AM, Benjamin Lerer 
wrote:

> +1
>
> On Fri, Apr 8, 2016 at 12:10 AM, 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://repository.apache.org/content/repositories/orgapachecassandra-1104/org/apache/cassandra/apache-cassandra/3.0.5/
> > Staging repository:
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1104/
> >
> > The artifacts as well as the debian package are also available here:
> > http://people.apache.org/~jake
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: http://goo.gl/f2b0Di (CHANGES.txt)
> > [2]: http://goo.gl/bHIeYj (NEWS.txt)
> > [3]: https://goo.gl/noLkHT (DataStax Test Report)
> >
>

Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-08 Thread Salih Gedik 

Hi,
I am wondering who are eligible to vote for these?
Thanks

+1

On Fri, Apr 8, 2016 at 9:24 AM, Benjamin Lerer 
wrote:


+1

On Fri, Apr 8, 2016 at 12:10 AM, 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://repository.apache.org/content/repositories/orgapachecassandra-1104/org/apache/cassandra/apache-cassandra/3.0.5/

Staging repository:


https://repository.apache.org/content/repositories/orgapachecassandra-1104/

The artifacts as well as the debian package are also available here:
http://people.apache.org/~jake

The vote will be open for 72 hours (longer if needed).

[1]: http://goo.gl/f2b0Di (CHANGES.txt)
[2]: http://goo.gl/bHIeYj (NEWS.txt)
[3]: https://goo.gl/noLkHT (DataStax Test Report)



--
Salih Gedik

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-08 Thread Sylvain Lebresne 
We also realized that some commits had been badly merge to trunk some times
ago (3.0 isn't affected) on
https://issues.apache.org/jira/browse/CASSANDRA-11353, so it also makes
sense to re-roll for those since they were supposed to be fixed a long time
ago and at least #11353 is worth not delaying further.
I'll note that we've already backported those missing tickets to the
cassandra-3.5 branch so we're good to re-roll from that branch as soon as
the SASI problem is fixed.

On Fri, Apr 8, 2016 at 2:54 AM, Jonathan Ellis  wrote:

> 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 3.5 we can
> > revert but it would be better to have 3.5 CASSANDRA-11383 +
> > CASSANDRA-11525.
> >
> > On Thu, Apr 7, 2016 at 3:48 PM, Pavel Yaskevich 
> wrote:
> >
> > > 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, 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, 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 <
> pove...@gmail.com>
> > >> > 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 Williams <
> > dri...@gmail.com>
> > >> > > wrote:
> > >> > > >
> > >> > > > > +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://repository.apache.org/content/repositories/orgapachecassandra-1105/org/apache/cassandra/apache-cassandra/3.5/
> > >> > > > > > Staging repository:
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> >
> > >>
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1105/
> > >> > > > > >
> > >> > > > > > The artifacts as well as the debian package are also
> available
> > >> > here:
> > >> > > > > > http://people.apache.org/~jake
> > >> > > > > >
> > >> > > > > > The vote will be open for 72 hours (longer if needed).
> > >> > > > > >
> > >> > > > > > [1]: http://goo.gl/v1sH4v (CHANGES.txt)
> > >> > > > > > [2]: http://goo.gl/ZlHf5z (NEWS.txt)
> > >> > > > > > [3]: https://goo.gl/hvPmFE (DataStax Test Report)
> > >> > > > > >
> > >> > > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> > >
> > >> > > --
> > >> > > Jonathan Ellis
> > >> > > Project Chair, Apache Cassandra
> > >> > > co-founder, http://www.datastax.com
> > >> > > @spyced
> > >> > >
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Jonathan Ellis
> > >> Project Chair, Apache Cassandra
> > >> co-founder, http://www.datastax.com
> > >> @spyced
> > >>
> > >
> > >
> >
>
>
>
> --
> Jonathan Ellis
> Project Chair, Apache Cassandra
> co-founder, http://www.datastax.com
> @spyced
>

Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-08 Thread Sylvain Lebresne 
On Fri, Apr 8, 2016 at 1:54 PM, Salih Gedik  wrote:

> Hi,
> I am wondering who are eligible to vote for these?
>

Officially, only PMC member (list here if you're interested:
https://projects.apache.org/committee.html?cassandra) votes are binding.
In practice though, we're grateful to anyone having tested the release in
its environment to come forward and tell us if they found a regression
specific to that version, or on the contrary if they have found no problems
in their testing. And of course, anyone is free to reply to the thread with
his +1 because he just think "cool, a new release", and we certainly don't
blame anyone for showing their enthusiasms, but just know it doesn't have
any official weight.



> Thanks
>
> +1
>>
>> On Fri, Apr 8, 2016 at 9:24 AM, Benjamin Lerer <
>> benjamin.le...@datastax.com>
>> wrote:
>>
>> +1
>>>
>>> On Fri, Apr 8, 2016 at 12:10 AM, 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://repository.apache.org/content/repositories/orgapachecassandra-1104/org/apache/cassandra/apache-cassandra/3.0.5/
>>>
 Staging repository:


>>> https://repository.apache.org/content/repositories/orgapachecassandra-1104/
>>>
 The artifacts as well as the debian package are also available here:
 http://people.apache.org/~jake

 The vote will be open for 72 hours (longer if needed).

 [1]: http://goo.gl/f2b0Di (CHANGES.txt)
 [2]: http://goo.gl/bHIeYj (NEWS.txt)
 [3]: https://goo.gl/noLkHT (DataStax Test Report)


> --
> Salih Gedik
>
>

Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-08 Thread Salih Gedik 

I see, Thank you for clearing up.

On Fri, Apr 8, 2016 at 1:54 PM, Salih Gedik  wrote:


Hi,
I am wondering who are eligible to vote for these?


Officially, only PMC member (list here if you're interested:
https://projects.apache.org/committee.html?cassandra) votes are binding.
In practice though, we're grateful to anyone having tested the release in
its environment to come forward and tell us if they found a regression
specific to that version, or on the contrary if they have found no problems
in their testing. And of course, anyone is free to reply to the thread with
his +1 because he just think "cool, a new release", and we certainly don't
blame anyone for showing their enthusiasms, but just know it doesn't have
any official weight.




Thanks

+1

On Fri, Apr 8, 2016 at 9:24 AM, Benjamin Lerer <
benjamin.le...@datastax.com>
wrote:

+1

On Fri, Apr 8, 2016 at 12:10 AM, 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://repository.apache.org/content/repositories/orgapachecassandra-1104/org/apache/cassandra/apache-cassandra/3.0.5/


Staging repository:



https://repository.apache.org/content/repositories/orgapachecassandra-1104/


The artifacts as well as the debian package are also available here:
http://people.apache.org/~jake

The vote will be open for 72 hours (longer if needed).

[1]: http://goo.gl/f2b0Di (CHANGES.txt)
[2]: http://goo.gl/bHIeYj (NEWS.txt)
[3]: https://goo.gl/noLkHT (DataStax Test Report)



--
Salih Gedik




--
Salih Gedik

Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-08 Thread Gary Dusbabek 
+1

On Thu, Apr 7, 2016 at 3: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://repository.apache.org/content/repositories/orgapachecassandra-1104/org/apache/cassandra/apache-cassandra/3.0.5/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1104/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/f2b0Di (CHANGES.txt)
> [2]: http://goo.gl/bHIeYj (NEWS.txt)
> [3]: https://goo.gl/noLkHT (DataStax Test Report)
>

[VOTE RESULT] Release Apache Cassandra 3.5

2016-04-08 Thread Jake Luciani 
The vota has failed. I'll send a new vote once the fixes are in and tests
completed.

On Fri, Apr 8, 2016 at 8:15 AM, Sylvain Lebresne 
wrote:

> We also realized that some commits had been badly merge to trunk some times
> ago (3.0 isn't affected) on
> https://issues.apache.org/jira/browse/CASSANDRA-11353, so it also makes
> sense to re-roll for those since they were supposed to be fixed a long time
> ago and at least #11353 is worth not delaying further.
> I'll note that we've already backported those missing tickets to the
> cassandra-3.5 branch so we're good to re-roll from that branch as soon as
> the SASI problem is fixed.
>
> On Fri, Apr 8, 2016 at 2:54 AM, Jonathan Ellis  wrote:
>
> > 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 3.5 we can
> > > revert but it would be better to have 3.5 CASSANDRA-11383 +
> > > CASSANDRA-11525.
> > >
> > > On Thu, Apr 7, 2016 at 3:48 PM, Pavel Yaskevich 
> > wrote:
> > >
> > > > 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, 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, 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 <
> > pove...@gmail.com>
> > > >> > 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 Williams <
> > > dri...@gmail.com>
> > > >> > > wrote:
> > > >> > > >
> > > >> > > > > +1
> > > >> > > > >
> > > >> > > > > On Thu, Apr 7, 2016 at 5:19 PM, Jake Luciani <
> j...@apache.org
> > >
> > > >> > 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://repository.apache.org/content/repositories/orgapachecassandra-1105/org/apache/cassandra/apache-cassandra/3.5/
> > > >> > > > > > Staging repository:
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1105/
> > > >> > > > > >
> > > >> > > > > > The artifacts as well as the debian package are also
> > available
> > > >> > here:
> > > >> > > > > > http://people.apache.org/~jake
> > > >> > > > > >
> > > >> > > > > > The vote will be open for 72 hours (longer if needed).
> > > >> > > > > >
> > > >> > > > > > [1]: http://goo.gl/v1sH4v (CHANGES.txt)
> > > >> > > > > > [2]: http://goo.gl/ZlHf5z (NEWS.txt)
> > > >> > > > > > [3]: https://goo.gl/hvPmFE (DataStax Test Report)
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Jonathan Ellis
> > > >> > > Project Chair, Apache Cassandra
> > > >> > > co-founder, http://www.datastax.com
> > > >> > > @spyced
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Jonathan Ellis
> > > >> Project Chair, Apache Cassandra
> > > >> co-founder, http://www.datastax.com
> > > >> @spyced
> > > >>
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Jonathan Ellis
> > Project Chair, Apache Cassandra
> > co-founder, http://www.datastax.com
> > @spyced
> >
>



-- 
http://twitter.com/tjake

Research on scalability bug finder for Cassandra

2016-04-08 Thread Tanakorn Leesatapornwongsa 
Dear Cassandra development team,

We are computer science researchers at the University of Chicago.  Our research 
is about the reliability of cloud-scale distributed systems. Samples of our 
work can be found here: http://ucare.cs.uchicago.edu 


We are reaching out to you because we are interested in reproducing any 
unsolved scalability bugs in Cassandra.

We define scalability bugs as latent bugs that are scale-dependent.  They don't 
arise in small-scale deployment but arise in large-scale production runs.  For 
example, everything is fine in 100-node deployment but in 500-node deployment 
the bug appears.

We have created a scale-check methodology (SLCK) that can unearth scalability 
bugs in a single machine.  With SLCK, we can run hundreds of nodes on a single 
machine and reproduce some old scalability bugs. For example, we have 
reproduced the following bugs in one machine:

- https://issues.apache.org/jira/browse/CASSANDRA-6127 
   (a customer observed 
node flapping when bootstrapping 1000 nodes)

- https://issues.apache.org/jira/browse/CASSANDRA-3831 


We are submitting SLCK for publication soon, and we can send you a draft a 
month from now if you are interested.

To make a stronger publication submission, beyond reproducing old bugs, we 
thought it would be great if SLCK can reproduce new scalability bugs (if any) 
that you are still trying to resolve.

We hope you find our work interesting and we would really appreciate if you can 
point to us any new scalability bugs that hopefully we can help you reproduce.

Thank you very much for your attention!

Best,
Tanakorn L.

Re: [VOTE] Release Apache Cassandra 3.0.5

2016-04-08 Thread Josh McKenzie 
+1

On Thu, Apr 7, 2016 at 6: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://repository.apache.org/content/repositories/orgapachecassandra-1104/org/apache/cassandra/apache-cassandra/3.0.5/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1104/
>
> The artifacts as well as the debian package are also available here:
> http://people.apache.org/~jake
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: http://goo.gl/f2b0Di (CHANGES.txt)
> [2]: http://goo.gl/bHIeYj (NEWS.txt)
> [3]: https://goo.gl/noLkHT (DataStax Test Report)
>

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-08 Thread Pavel Yaskevich 
Alright, we've figured what the problem is in CASSANDRA-11525, I'm running
last tests on my machine, going to push changes into my branch soon, wait
for dtest/testall to run and merge later tonight.
So we should be on track for 3.5 vote tomorrow.

On Fri, Apr 8, 2016 at 5:15 AM, Sylvain Lebresne 
wrote:

> We also realized that some commits had been badly merge to trunk some times
> ago (3.0 isn't affected) on
> https://issues.apache.org/jira/browse/CASSANDRA-11353, so it also makes
> sense to re-roll for those since they were supposed to be fixed a long time
> ago and at least #11353 is worth not delaying further.
> I'll note that we've already backported those missing tickets to the
> cassandra-3.5 branch so we're good to re-roll from that branch as soon as
> the SASI problem is fixed.
>
> On Fri, Apr 8, 2016 at 2:54 AM, Jonathan Ellis  wrote:
>
> > 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 3.5 we can
> > > revert but it would be better to have 3.5 CASSANDRA-11383 +
> > > CASSANDRA-11525.
> > >
> > > On Thu, Apr 7, 2016 at 3:48 PM, Pavel Yaskevich 
> > wrote:
> > >
> > > > 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, 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, 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 <
> > pove...@gmail.com>
> > > >> > 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 Williams <
> > > dri...@gmail.com>
> > > >> > > wrote:
> > > >> > > >
> > > >> > > > > +1
> > > >> > > > >
> > > >> > > > > On Thu, Apr 7, 2016 at 5:19 PM, Jake Luciani <
> j...@apache.org
> > >
> > > >> > 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://repository.apache.org/content/repositories/orgapachecassandra-1105/org/apache/cassandra/apache-cassandra/3.5/
> > > >> > > > > > Staging repository:
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> >
> > > >>
> > >
> >
> https://repository.apache.org/content/repositories/orgapachecassandra-1105/
> > > >> > > > > >
> > > >> > > > > > The artifacts as well as the debian package are also
> > available
> > > >> > here:
> > > >> > > > > > http://people.apache.org/~jake
> > > >> > > > > >
> > > >> > > > > > The vote will be open for 72 hours (longer if needed).
> > > >> > > > > >
> > > >> > > > > > [1]: http://goo.gl/v1sH4v (CHANGES.txt)
> > > >> > > > > > [2]: http://goo.gl/ZlHf5z (NEWS.txt)
> > > >> > > > > > [3]: https://goo.gl/hvPmFE (DataStax Test Report)
> > > >> > > > > >
> > > >> > > > >
> > > >> > > >
> > > >> > >
> > > >> > >
> > > >> > >
> > > >> > > --
> > > >> > > Jonathan Ellis
> > > >> > > Project Chair, Apache Cassandra
> > > >> > > co-founder, http://www.datastax.com
> > > >> > > @spyced
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >>
> > > >> --
> > > >> Jonathan Ellis
> > > >> Project Chair, Apache Cassandra
> > > >> co-founder, http://www.datastax.com
> > > >> @spyced
> > > >>
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Jonathan Ellis
> > Project Chair, Apache Cassandra
> > co-founder, http://www.datastax.com
> > @spyced
> >
>

Re: Research on scalability bug finder for Cassandra

2016-04-08 Thread Jonathan Ellis 
Sounds very interesting!  We'd love to hear more about your approach.  In
particular, does it require a patched version of Cassandra?

On Thu, Apr 7, 2016 at 6:18 PM, Tanakorn Leesatapornwongsa <
tanak...@cs.uchicago.edu> wrote:

> Dear Cassandra development team,
>
> We are computer science researchers at the University of Chicago.  Our
> research is about the reliability of cloud-scale distributed systems.
> Samples of our work can be found here: http://ucare.cs.uchicago.edu <
> http://ucare.cs.uchicago.edu/>
>
> We are reaching out to you because we are interested in reproducing any
> unsolved scalability bugs in Cassandra.
>
> We define scalability bugs as latent bugs that are scale-dependent.  They
> don't arise in small-scale deployment but arise in large-scale production
> runs.  For example, everything is fine in 100-node deployment but in
> 500-node deployment the bug appears.
>
> We have created a scale-check methodology (SLCK) that can unearth
> scalability bugs in a single machine.  With SLCK, we can run hundreds of
> nodes on a single machine and reproduce some old scalability bugs. For
> example, we have reproduced the following bugs in one machine:
>
> - https://issues.apache.org/jira/browse/CASSANDRA-6127 <
> https://issues.apache.org/jira/browse/CASSANDRA-6127>   (a customer
> observed node flapping when bootstrapping 1000 nodes)
>
> - https://issues.apache.org/jira/browse/CASSANDRA-3831 <
> https://issues.apache.org/jira/browse/CASSANDRA-3831>
>
> We are submitting SLCK for publication soon, and we can send you a draft a
> month from now if you are interested.
>
> To make a stronger publication submission, beyond reproducing old bugs, we
> thought it would be great if SLCK can reproduce new scalability bugs (if
> any) that you are still trying to resolve.
>
> We hope you find our work interesting and we would really appreciate if
> you can point to us any new scalability bugs that hopefully we can help you
> reproduce.
>
> Thank you very much for your attention!
>
> Best,
> Tanakorn L.
>
>
>
>


-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder, http://www.datastax.com
@spyced

Re: [VOTE] Release Apache Cassandra 3.5

2016-04-08 Thread Pavel Yaskevich 
CASSANDRA-11525 is resolved now, I think we can restart the vote if that
was the only blocker.

On Fri, Apr 8, 2016 at 5:57 PM, Pavel Yaskevich  wrote:

> Alright, we've figured what the problem is in CASSANDRA-11525, I'm running
> last tests on my machine, going to push changes into my branch soon, wait
> for dtest/testall to run and merge later tonight.
> So we should be on track for 3.5 vote tomorrow.
>
> On Fri, Apr 8, 2016 at 5:15 AM, Sylvain Lebresne 
> wrote:
>
>> We also realized that some commits had been badly merge to trunk some
>> times
>> ago (3.0 isn't affected) on
>> https://issues.apache.org/jira/browse/CASSANDRA-11353, so it also makes
>> sense to re-roll for those since they were supposed to be fixed a long
>> time
>> ago and at least #11353 is worth not delaying further.
>> I'll note that we've already backported those missing tickets to the
>> cassandra-3.5 branch so we're good to re-roll from that branch as soon as
>> the SASI problem is fixed.
>>
>> On Fri, Apr 8, 2016 at 2:54 AM, Jonathan Ellis  wrote:
>>
>> > 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 3.5 we can
>> > > revert but it would be better to have 3.5 CASSANDRA-11383 +
>> > > CASSANDRA-11525.
>> > >
>> > > On Thu, Apr 7, 2016 at 3:48 PM, Pavel Yaskevich 
>> > wrote:
>> > >
>> > > > 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, 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, Apr 7, 2016 at 3:35 PM, Jonathan Ellis <
>> jbel...@gmail.com>
>> > > >> wrote:
>> > > >> >
>> > > >> > > So it's a new regression, not present in 3.4?
>> > > >> > >
>> > > >> > > On Thu, Apr 7, 2016 at 5:24 PM, Pavel Yaskevich <
>> > pove...@gmail.com>
>> > > >> > 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 Williams <
>> > > dri...@gmail.com>
>> > > >> > > wrote:
>> > > >> > > >
>> > > >> > > > > +1
>> > > >> > > > >
>> > > >> > > > > On Thu, Apr 7, 2016 at 5:19 PM, Jake Luciani <
>> j...@apache.org
>> > >
>> > > >> > 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://repository.apache.org/content/repositories/orgapachecassandra-1105/org/apache/cassandra/apache-cassandra/3.5/
>> > > >> > > > > > Staging repository:
>> > > >> > > > > >
>> > > >> > > > >
>> > > >> > > >
>> > > >> > >
>> > > >> >
>> > > >>
>> > >
>> >
>> https://repository.apache.org/content/repositories/orgapachecassandra-1105/
>> > > >> > > > > >
>> > > >> > > > > > The artifacts as well as the debian package are also
>> > available
>> > > >> > here:
>> > > >> > > > > > http://people.apache.org/~jake
>> > > >> > > > > >
>> > > >> > > > > > The vote will be open for 72 hours (longer if needed).
>> > > >> > > > > >
>> > > >> > > > > > [1]: http://goo.gl/v1sH4v (CHANGES.txt)
>> > > >> > > > > > [2]: http://goo.gl/ZlHf5z (NEWS.txt)
>> > > >> > > > > > [3]: https://goo.gl/hvPmFE (DataStax Test Report)
>> > > >> > > > > >
>> > > >> > > > >
>> > > >> > > >
>> > > >> > >
>> > > >> > >
>> > > >> > >
>> > > >> > > --
>> > > >> > > Jonathan Ellis
>> > > >> > > Project Chair, Apache Cassandra
>> > > >> > > co-founder, http://www.datastax.com
>> > > >> > > @spyced
>> > > >> > >
>> > > >> >
>> > > >>
>> > > >>
>> > > >>
>> > > >> --
>> > > >> Jonathan Ellis
>> > > >> Project Chair, Apache Cassandra
>> > > >> co-founder, http://www.datastax.com
>> > > >> @spyced
>> > > >>
>> > > >
>> > > >
>> > >
>> >
>> >
>> >
>> > --
>> > Jonathan Ellis
>> > Project Chair, Apache Cassandra
>> > co-founder, http://www.datastax.com
>> > @spyce