Re: [VOTE] (Take 3) Release Apache Cassandra 3.11.2

[Jason Brown]

I ran the unit tests and they are green:
https://circleci.com/gh/jasobrown/workflows/cassandra/tree/3.11.2-candidate-2

+1. Thanks, Michael.

On Wed, Feb 14, 2018 at 1:34 PM, Nate McCall  wrote:

> +1
>
> On Thu, Feb 15, 2018 at 10:09 AM, Michael Shuler 
> wrote:
> > I propose the following artifacts for release as 3.11.2.
> >
> > sha1: 1d506f9d09c880ff2b2693e3e27fa58c02ecf398
> > Git:
> > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
> shortlog;h=refs/tags/3.11.2-tentative
> > Artifacts:
> > https://repository.apache.org/content/repositories/
> orgapachecassandra-1158/org/apache/cassandra/apache-cassandra/3.11.2/
> > Staging repository:
> > https://repository.apache.org/content/repositories/
> orgapachecassandra-1158/
> >
> > Debian and RPM packages are available here:
> > http://people.apache.org/~mshuler
> >
> > *** This release addresses an important fix for CASSANDRA-14092 ***
> > "Max ttl of 20 years will overflow localDeletionTime"
> > https://issues.apache.org/jira/browse/CASSANDRA-14092
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: (CHANGES.txt) https://goo.gl/RLZLrR
> > [2]: (NEWS.txt) https://goo.gl/kpnVHp
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: [VOTE] (Take 3) Release Apache Cassandra 3.11.2

[Nate McCall]

+1

On Thu, Feb 15, 2018 at 10:09 AM, Michael Shuler  wrote:
> I propose the following artifacts for release as 3.11.2.
>
> sha1: 1d506f9d09c880ff2b2693e3e27fa58c02ecf398
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.2-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1158/org/apache/cassandra/apache-cassandra/3.11.2/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1158/
>
> Debian and RPM packages are available here:
> http://people.apache.org/~mshuler
>
> *** This release addresses an important fix for CASSANDRA-14092 ***
> "Max ttl of 20 years will overflow localDeletionTime"
> https://issues.apache.org/jira/browse/CASSANDRA-14092
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: (CHANGES.txt) https://goo.gl/RLZLrR
> [2]: (NEWS.txt) https://goo.gl/kpnVHp
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] (Take 2) Release Apache Cassandra 3.0.16

[Nate McCall]

+1

On Thu, Feb 15, 2018 at 9:40 AM, Michael Shuler  wrote:
> I propose the following artifacts for release as 3.0.16.
>
> sha1: 890f319142ddd3cf2692ff45ff28e71001365e96
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.16-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1157/org/apache/cassandra/apache-cassandra/3.0.16/
> Staging repository:
> https://repository.apache.org/content/repositories/orgapachecassandra-1157/
>
> Debian and RPM packages are available here:
> http://people.apache.org/~mshuler
>
> *** This release addresses an important fix for CASSANDRA-14092 ***
> "Max ttl of 20 years will overflow localDeletionTime"
> https://issues.apache.org/jira/browse/CASSANDRA-14092
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: (CHANGES.txt) https://goo.gl/rLj59Z
> [2]: (NEWS.txt) https://goo.gl/EkrT4G
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] (Take 3) Release Apache Cassandra 3.11.2

[Brandon Williams]

+1

On Wed, Feb 14, 2018 at 3:09 PM, Michael Shuler 
wrote:

> I propose the following artifacts for release as 3.11.2.
>
> sha1: 1d506f9d09c880ff2b2693e3e27fa58c02ecf398
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
> shortlog;h=refs/tags/3.11.2-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/
> orgapachecassandra-1158/org/apache/cassandra/apache-cassandra/3.11.2/
> Staging repository:
> https://repository.apache.org/content/repositories/
> orgapachecassandra-1158/
>
> Debian and RPM packages are available here:
> http://people.apache.org/~mshuler
>
> *** This release addresses an important fix for CASSANDRA-14092 ***
> "Max ttl of 20 years will overflow localDeletionTime"
> https://issues.apache.org/jira/browse/CASSANDRA-14092
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: (CHANGES.txt) https://goo.gl/RLZLrR
> [2]: (NEWS.txt) https://goo.gl/kpnVHp
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

Re: [VOTE] (Take 2) Release Apache Cassandra 3.0.16

[Jason Brown]

I ran the unit tests, and all are green:
https://circleci.com/gh/jasobrown/workflows/cassandra/tree/3.0.16-candidate-2

+1. Thank you, Michael.

On Wed, Feb 14, 2018 at 12:51 PM, Brandon Williams  wrote:

> +1
>
> On Wed, Feb 14, 2018 at 2:40 PM, Michael Shuler 
> wrote:
>
> > I propose the following artifacts for release as 3.0.16.
> >
> > sha1: 890f319142ddd3cf2692ff45ff28e71001365e96
> > Git:
> > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
> > shortlog;h=refs/tags/3.0.16-tentative
> > Artifacts:
> > https://repository.apache.org/content/repositories/
> > orgapachecassandra-1157/org/apache/cassandra/apache-cassandra/3.0.16/
> > Staging repository:
> > https://repository.apache.org/content/repositories/
> > orgapachecassandra-1157/
> >
> > Debian and RPM packages are available here:
> > http://people.apache.org/~mshuler
> >
> > *** This release addresses an important fix for CASSANDRA-14092 ***
> > "Max ttl of 20 years will overflow localDeletionTime"
> > https://issues.apache.org/jira/browse/CASSANDRA-14092
> >
> > The vote will be open for 72 hours (longer if needed).
> >
> > [1]: (CHANGES.txt) https://goo.gl/rLj59Z
> > [2]: (NEWS.txt) https://goo.gl/EkrT4G
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
>

Re: [VOTE] (Take 2) Release Apache Cassandra 3.0.16

[Brandon Williams]

+1

On Wed, Feb 14, 2018 at 2:40 PM, Michael Shuler 
wrote:

> I propose the following artifacts for release as 3.0.16.
>
> sha1: 890f319142ddd3cf2692ff45ff28e71001365e96
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
> shortlog;h=refs/tags/3.0.16-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/
> orgapachecassandra-1157/org/apache/cassandra/apache-cassandra/3.0.16/
> Staging repository:
> https://repository.apache.org/content/repositories/
> orgapachecassandra-1157/
>
> Debian and RPM packages are available here:
> http://people.apache.org/~mshuler
>
> *** This release addresses an important fix for CASSANDRA-14092 ***
> "Max ttl of 20 years will overflow localDeletionTime"
> https://issues.apache.org/jira/browse/CASSANDRA-14092
>
> The vote will be open for 72 hours (longer if needed).
>
> [1]: (CHANGES.txt) https://goo.gl/rLj59Z
> [2]: (NEWS.txt) https://goo.gl/EkrT4G
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

[VOTE] (Take 2) Release Apache Cassandra 3.0.16

[Michael Shuler]

I propose the following artifacts for release as 3.0.16.

sha1: 890f319142ddd3cf2692ff45ff28e71001365e96
Git:
http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.16-tentative
Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1157/org/apache/cassandra/apache-cassandra/3.0.16/
Staging repository:
https://repository.apache.org/content/repositories/orgapachecassandra-1157/

Debian and RPM packages are available here:
http://people.apache.org/~mshuler

*** This release addresses an important fix for CASSANDRA-14092 ***
"Max ttl of 20 years will overflow localDeletionTime"
https://issues.apache.org/jira/browse/CASSANDRA-14092

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

[1]: (CHANGES.txt) https://goo.gl/rLj59Z
[2]: (NEWS.txt) https://goo.gl/EkrT4G

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

[Michael Kjellman]

No worries.. it looks like we didn't update the circleci config in tree for the 
cassandra-3.0 and cassandra-3.11 branches. We should do that -- i'll take that 
as an action item on me... for now though you can grab the same one from trunk:

CircleCI Configuration: 
https://github.com/apache/cassandra/blob/trunk/.circleci/config.yml

FYI: kjellman/cassandra-test:0.4.3 is was built from the Docker file as 
committed here: 
https://github.com/mkjellman/cassandra-test-docker/blob/master/Dockerfile

best,
kjellman

On Feb 14, 2018, at 10:24 AM, Michael Shuler 
> wrote:

I apologize for being naive. The test runs do not come from the in-tree
circle.yml file and I need to do something different?

On 02/14/2018 12:21 PM, Michael Kjellman wrote:
please use the latest circleci config that is in trunk. looking at the config 
you used in your run you’re using the old circleci 1.0 based config.

On Feb 14, 2018, at 10:16 AM, Michael Shuler 
> wrote:

So far, I have had very unpredictable test runs from CirceCI and ASF
Jenkins. Commit 890f319 resulted in 4 completely different test failures
for me today in CircleCI.

https://circleci.com/gh/mshuler/cassandra/150

I trust results from the static ASF slaves even less.

`ant test-all -Dtest.name=CommitLogSegmentBackpressureTest` passed for
me locally.

¯\_(ツ)_/¯

I do not see any permissions issues in the output of this repeating test
failure from our internal Jenkins, but it appears that an instance of
Cassandra is left running from some other test, perhaps, and this test
cannot bind.

I'm fine with cutting a new release set from 890f319 and chalking this
up to test flakiness.

--
Kind regards,
Michael

On 02/14/2018 11:50 AM, Michael Kjellman wrote:
the tests are writing something to java.io.tmpdir which for whatever reason 
isn’t writable. the same exact tests work locally and in the cassandra-test 
docker image.

given everyone can partake on circleci runs and asf jenkins i think we should 
send out those links and base the vote off those runs.

On Feb 14, 2018, at 9:48 AM, Michael Shuler  wrote:

This is an internal Jenkins instance that's not reachable on the internet.

What's the permissions issue? The test runs on this internal instance
are exactly the way cassci used to run - launch a scratch machine, check
out, build, run tests.

I'll see if I can repro locally.

Michael

On 02/14/2018 11:44 AM, Michael Kjellman wrote:
i looked at this a few weeks back. this is asf jenkins right? if so, it’s a 
permissions issue on the build executors

On Feb 14, 2018, at 9:40 AM, Michael Shuler  wrote:

Thanks for the feedback on 3.0.16 tentative release.

Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test
(in both standard and -compression suites) in CI for me. This test has
failed 20 times in the last 20 runs. Test output attached.

Do we wish to fix this before the next cut, since we're here? :)

--
Kind regards,
Michael

On 02/14/2018 07:30 AM, Jason Brown wrote:
I think we can attempt another build and vote now.

On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown  wrote:

CASSANDRA-14219 is committed and tests look clean (https://circleci.com/
workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f).

On Tue, Feb 13, 2018 at 1:47 PM, Brandon Williams 
wrote:

I change my vote to -1 binding as well.

On Tue, Feb 13, 2018 at 3:43 PM, Jason Brown 
wrote:

-1, binding. Unit tests are broken:
https://circleci.com/gh/jasobrown/cassandra/451#tests/containers/50

Dave ninja-committed 7df36056b12a13b60097b7a9a4f8155a1d02ff62 to update
some logging messages, which broke ViewComplexTest. The errors like
this:

junit.framework.AssertionFailedError: Expected error message to contain
'Cannot drop column a on base table with materialized views', but got
'Cannot drop column a on base table table_21 with materialized views.'

Dave has a followup commit, 40148a178bd9b74b731591aa46b4158efb16b742,
which
fixed a few of the errors, but there are four outstanding failures. I
created CASSANDRA-14219 last week, and assigned it to Dave, but he might
have missed the notification. Dinesh Joshi has a patch that I will
review
ASAP.

Michael, is there a link of where you ran the tests? If so, can you
include
it in the future [VOTE] emails?

Thanks,

-Jason



On Tue, Feb 13, 2018 at 11:03 AM, Jon Haddad  wrote:

+1

On Feb 13, 2018, at 10:52 AM, Josh McKenzie 
wrote:

+1

On Feb 13, 2018 9:20 AM, "Marcus Eriksson" 
wrote:

+1

On Tue, Feb 13, 2018 at 1:29 PM, Aleksey Yeshchenko <
alek...@apple.com>
wrote:

+1

—
AY

On 12 February 2018 at 20:31:23, Michael Shuler (
mich...@pbandjelly.org)
wrote:

I propose the following artifacts for release as 3.0.16.

sha1: 91e83c72de109521074b14a8eeae1309c3b1f215
Git:

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

[Michael Kjellman]

please use the latest circleci config that is in trunk. looking at the config 
you used in your run you’re using the old circleci 1.0 based config. 

> On Feb 14, 2018, at 10:16 AM, Michael Shuler  wrote:
> 
> So far, I have had very unpredictable test runs from CirceCI and ASF
> Jenkins. Commit 890f319 resulted in 4 completely different test failures
> for me today in CircleCI.
> 
> https://circleci.com/gh/mshuler/cassandra/150
> 
> I trust results from the static ASF slaves even less.
> 
> `ant test-all -Dtest.name=CommitLogSegmentBackpressureTest` passed for
> me locally.
> 
>  ¯\_(ツ)_/¯
> 
> I do not see any permissions issues in the output of this repeating test
> failure from our internal Jenkins, but it appears that an instance of
> Cassandra is left running from some other test, perhaps, and this test
> cannot bind.
> 
> I'm fine with cutting a new release set from 890f319 and chalking this
> up to test flakiness.
> 
> -- 
> Kind regards,
> Michael
> 
>> On 02/14/2018 11:50 AM, Michael Kjellman wrote:
>> the tests are writing something to java.io.tmpdir which for whatever reason 
>> isn’t writable. the same exact tests work locally and in the cassandra-test 
>> docker image.
>> 
>> given everyone can partake on circleci runs and asf jenkins i think we 
>> should send out those links and base the vote off those runs.
>> 
>>> On Feb 14, 2018, at 9:48 AM, Michael Shuler  wrote:
>>> 
>>> This is an internal Jenkins instance that's not reachable on the internet.
>>> 
>>> What's the permissions issue? The test runs on this internal instance
>>> are exactly the way cassci used to run - launch a scratch machine, check
>>> out, build, run tests.
>>> 
>>> I'll see if I can repro locally.
>>> 
>>> Michael
>>> 
 On 02/14/2018 11:44 AM, Michael Kjellman wrote:
 i looked at this a few weeks back. this is asf jenkins right? if so, it’s 
 a permissions issue on the build executors 
 
> On Feb 14, 2018, at 9:40 AM, Michael Shuler  
> wrote:
> 
> Thanks for the feedback on 3.0.16 tentative release.
> 
> Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test
> (in both standard and -compression suites) in CI for me. This test has
> failed 20 times in the last 20 runs. Test output attached.
> 
> Do we wish to fix this before the next cut, since we're here? :)
> 
> -- 
> Kind regards,
> Michael
> 
>> On 02/14/2018 07:30 AM, Jason Brown wrote:
>> I think we can attempt another build and vote now.
>> 
>>> On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown  
>>> wrote:
>>> 
>>> CASSANDRA-14219 is committed and tests look clean (https://circleci.com/
>>> workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f).
>>> 
>>> On Tue, Feb 13, 2018 at 1:47 PM, Brandon Williams 
>>> wrote:
>>> 
 I change my vote to -1 binding as well.
 
 On Tue, Feb 13, 2018 at 3:43 PM, Jason Brown 
 wrote:
 
> -1, binding. Unit tests are broken:
> https://circleci.com/gh/jasobrown/cassandra/451#tests/containers/50
> 
> Dave ninja-committed 7df36056b12a13b60097b7a9a4f8155a1d02ff62 to 
> update
> some logging messages, which broke ViewComplexTest. The errors like
 this:
> 
> junit.framework.AssertionFailedError: Expected error message to 
> contain
> 'Cannot drop column a on base table with materialized views', but got
> 'Cannot drop column a on base table table_21 with materialized views.'
> 
> Dave has a followup commit, 40148a178bd9b74b731591aa46b4158efb16b742,
> which
> fixed a few of the errors, but there are four outstanding failures. I
> created CASSANDRA-14219 last week, and assigned it to Dave, but he 
> might
> have missed the notification. Dinesh Joshi has a patch that I will
 review
> ASAP.
> 
> Michael, is there a link of where you ran the tests? If so, can you
 include
> it in the future [VOTE] emails?
> 
> Thanks,
> 
> -Jason
> 
> 
> 
>> On Tue, Feb 13, 2018 at 11:03 AM, Jon Haddad  
>> wrote:
>> 
>> +1
>> 
>>> On Feb 13, 2018, at 10:52 AM, Josh McKenzie 
>> wrote:
>>> 
>>> +1
>>> 
>>> On Feb 13, 2018 9:20 AM, "Marcus Eriksson" 
 wrote:
>>> 
 +1
 
 On Tue, Feb 13, 2018 at 1:29 PM, Aleksey Yeshchenko <
> alek...@apple.com>
 wrote:
 
> +1
> 
> —
> AY
> 
> On 12 February 2018 at 20:31:23, 

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

[Michael Kjellman]

the tests are writing something to java.io.tmpdir which for whatever reason 
isn’t writable. the same exact tests work locally and in the cassandra-test 
docker image.

given everyone can partake on circleci runs and asf jenkins i think we should 
send out those links and base the vote off those runs.

> On Feb 14, 2018, at 9:48 AM, Michael Shuler  wrote:
> 
> This is an internal Jenkins instance that's not reachable on the internet.
> 
> What's the permissions issue? The test runs on this internal instance
> are exactly the way cassci used to run - launch a scratch machine, check
> out, build, run tests.
> 
> I'll see if I can repro locally.
> 
> Michael
> 
>> On 02/14/2018 11:44 AM, Michael Kjellman wrote:
>> i looked at this a few weeks back. this is asf jenkins right? if so, it’s a 
>> permissions issue on the build executors 
>> 
>>> On Feb 14, 2018, at 9:40 AM, Michael Shuler  wrote:
>>> 
>>> Thanks for the feedback on 3.0.16 tentative release.
>>> 
>>> Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test
>>> (in both standard and -compression suites) in CI for me. This test has
>>> failed 20 times in the last 20 runs. Test output attached.
>>> 
>>> Do we wish to fix this before the next cut, since we're here? :)
>>> 
>>> -- 
>>> Kind regards,
>>> Michael
>>> 
 On 02/14/2018 07:30 AM, Jason Brown wrote:
 I think we can attempt another build and vote now.
 
> On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown  wrote:
> 
> CASSANDRA-14219 is committed and tests look clean (https://circleci.com/
> workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f).
> 
> On Tue, Feb 13, 2018 at 1:47 PM, Brandon Williams 
> wrote:
> 
>> I change my vote to -1 binding as well.
>> 
>> On Tue, Feb 13, 2018 at 3:43 PM, Jason Brown 
>> wrote:
>> 
>>> -1, binding. Unit tests are broken:
>>> https://circleci.com/gh/jasobrown/cassandra/451#tests/containers/50
>>> 
>>> Dave ninja-committed 7df36056b12a13b60097b7a9a4f8155a1d02ff62 to update
>>> some logging messages, which broke ViewComplexTest. The errors like
>> this:
>>> 
>>> junit.framework.AssertionFailedError: Expected error message to contain
>>> 'Cannot drop column a on base table with materialized views', but got
>>> 'Cannot drop column a on base table table_21 with materialized views.'
>>> 
>>> Dave has a followup commit, 40148a178bd9b74b731591aa46b4158efb16b742,
>>> which
>>> fixed a few of the errors, but there are four outstanding failures. I
>>> created CASSANDRA-14219 last week, and assigned it to Dave, but he might
>>> have missed the notification. Dinesh Joshi has a patch that I will
>> review
>>> ASAP.
>>> 
>>> Michael, is there a link of where you ran the tests? If so, can you
>> include
>>> it in the future [VOTE] emails?
>>> 
>>> Thanks,
>>> 
>>> -Jason
>>> 
>>> 
>>> 
 On Tue, Feb 13, 2018 at 11:03 AM, Jon Haddad  
 wrote:
 
 +1
 
> On Feb 13, 2018, at 10:52 AM, Josh McKenzie 
 wrote:
> 
> +1
> 
> On Feb 13, 2018 9:20 AM, "Marcus Eriksson" 
>> wrote:
> 
>> +1
>> 
>> On Tue, Feb 13, 2018 at 1:29 PM, Aleksey Yeshchenko <
>>> alek...@apple.com>
>> wrote:
>> 
>>> +1
>>> 
>>> —
>>> AY
>>> 
>>> On 12 February 2018 at 20:31:23, Michael Shuler (
 mich...@pbandjelly.org)
>>> wrote:
>>> 
>>> I propose the following artifacts for release as 3.0.16.
>>> 
>>> sha1: 91e83c72de109521074b14a8eeae1309c3b1f215
>>> Git:
>>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
>>> shortlog;h=refs/tags/3.0.16-tentative
>>> Artifacts:
>>> https://repository.apache.org/content/repositories/
>>> orgapachecassandra-1154/org/apache/cassandra/apache-
>>> cassandra/3.0.16/
>>> Staging repository:
>>> https://repository.apache.org/content/repositories/
>>> orgapachecassandra-1154/
>>> 
>>> Debian and RPM packages are available here:
>>> http://people.apache.org/~mshuler
>>> 
>>> *** This release addresses an important fix for CASSANDRA-14092
>> ***
>>> "Max ttl of 20 years will overflow localDeletionTime"
>>> https://issues.apache.org/jira/browse/CASSANDRA-14092
>>> 
>>> The vote will be open for 72 hours (longer if needed).
>>> 
>>> [1]: (CHANGES.txt) https://goo.gl/rLj59Z
>>> [2]: (NEWS.txt) https://goo.gl/EkrT4G
>>> 
>>> 
>> 
 
 
 

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

[Michael Shuler]

This is an internal Jenkins instance that's not reachable on the internet.

What's the permissions issue? The test runs on this internal instance
are exactly the way cassci used to run - launch a scratch machine, check
out, build, run tests.

I'll see if I can repro locally.

Michael

On 02/14/2018 11:44 AM, Michael Kjellman wrote:
> i looked at this a few weeks back. this is asf jenkins right? if so, it’s a 
> permissions issue on the build executors 
> 
>> On Feb 14, 2018, at 9:40 AM, Michael Shuler  wrote:
>>
>> Thanks for the feedback on 3.0.16 tentative release.
>>
>> Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test
>> (in both standard and -compression suites) in CI for me. This test has
>> failed 20 times in the last 20 runs. Test output attached.
>>
>> Do we wish to fix this before the next cut, since we're here? :)
>>
>> -- 
>> Kind regards,
>> Michael
>>
>>> On 02/14/2018 07:30 AM, Jason Brown wrote:
>>> I think we can attempt another build and vote now.
>>>
 On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown  wrote:

 CASSANDRA-14219 is committed and tests look clean (https://circleci.com/
 workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f).

 On Tue, Feb 13, 2018 at 1:47 PM, Brandon Williams 
 wrote:

> I change my vote to -1 binding as well.
>
> On Tue, Feb 13, 2018 at 3:43 PM, Jason Brown 
> wrote:
>
>> -1, binding. Unit tests are broken:
>> https://circleci.com/gh/jasobrown/cassandra/451#tests/containers/50
>>
>> Dave ninja-committed 7df36056b12a13b60097b7a9a4f8155a1d02ff62 to update
>> some logging messages, which broke ViewComplexTest. The errors like
> this:
>>
>> junit.framework.AssertionFailedError: Expected error message to contain
>> 'Cannot drop column a on base table with materialized views', but got
>> 'Cannot drop column a on base table table_21 with materialized views.'
>>
>> Dave has a followup commit, 40148a178bd9b74b731591aa46b4158efb16b742,
>> which
>> fixed a few of the errors, but there are four outstanding failures. I
>> created CASSANDRA-14219 last week, and assigned it to Dave, but he might
>> have missed the notification. Dinesh Joshi has a patch that I will
> review
>> ASAP.
>>
>> Michael, is there a link of where you ran the tests? If so, can you
> include
>> it in the future [VOTE] emails?
>>
>> Thanks,
>>
>> -Jason
>>
>>
>>
>>> On Tue, Feb 13, 2018 at 11:03 AM, Jon Haddad  wrote:
>>>
>>> +1
>>>
 On Feb 13, 2018, at 10:52 AM, Josh McKenzie 
>>> wrote:

 +1

 On Feb 13, 2018 9:20 AM, "Marcus Eriksson" 
> wrote:

> +1
>
> On Tue, Feb 13, 2018 at 1:29 PM, Aleksey Yeshchenko <
>> alek...@apple.com>
> wrote:
>
>> +1
>>
>> —
>> AY
>>
>> On 12 February 2018 at 20:31:23, Michael Shuler (
>>> mich...@pbandjelly.org)
>> wrote:
>>
>> I propose the following artifacts for release as 3.0.16.
>>
>> sha1: 91e83c72de109521074b14a8eeae1309c3b1f215
>> Git:
>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
>> shortlog;h=refs/tags/3.0.16-tentative
>> Artifacts:
>> https://repository.apache.org/content/repositories/
>> orgapachecassandra-1154/org/apache/cassandra/apache-
>> cassandra/3.0.16/
>> Staging repository:
>> https://repository.apache.org/content/repositories/
>> orgapachecassandra-1154/
>>
>> Debian and RPM packages are available here:
>> http://people.apache.org/~mshuler
>>
>> *** This release addresses an important fix for CASSANDRA-14092
> ***
>> "Max ttl of 20 years will overflow localDeletionTime"
>> https://issues.apache.org/jira/browse/CASSANDRA-14092
>>
>> The vote will be open for 72 hours (longer if needed).
>>
>> [1]: (CHANGES.txt) https://goo.gl/rLj59Z
>> [2]: (NEWS.txt) https://goo.gl/EkrT4G
>>
>>
>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>>>
>>>
>>
>


>>>
>>
>> <3.0-890f319-testall-failure.txt>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: dev-h...@cassandra.apache.org
> 
> -
> To unsubscribe, e-mail: 

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

[Michael Shuler]

On 02/14/2018 11:40 AM, Michael Shuler wrote:
> Thanks for the feedback on 3.0.16 tentative release.
> 
> Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test
> (in both standard and -compression suites) in CI for me. This test has
> failed 20 times in the last 20 runs. Test output attached.
> 
> Do we wish to fix this before the next cut, since we're here? :)
> 

This looks like the commit on the first
testCompressedCommitLogBackpressure failure, looking back through CI
history:
https://github.com/apache/cassandra/commit/db788fe860dfd69f06ab97ae35fa67fcf2517b6d



-- 
Michael

-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: row tombstones as a separate sstable citizen

[Carl Mueller]

So is this at least a decent candidate for a feature request ticket?


On Tue, Feb 13, 2018 at 8:09 PM, Carl Mueller 
wrote:

> I'm particularly interested in getting the tombstones to "promote" up the
> levels of LCS more quickly. Currently they get attached at the low level
> and don't propagate up to higher levels until enough activity at a lower
> level promotes the data. Meanwhile, LCS means compactions can occur in
> parallel at each level. So row tombstones in their own sstable could be up
> promoted the LCS levels preferentially before normal processes would move
> them up.
>
> So if the delete-only sstables could move up more quickly, the compaction
> at the levels would happen more quickly.
>
> The threshold stuff is nice if I read 7019 correctly, but what is the %
> there? % of rows? % of columns? or % of the size of the sstable? Row
> tombstones are pretty compact being just the rowkey and the tombstone
> marker. So if 7019 is triggered at 10% of the sstable size, even a crapton
> of tombstones deleting practially the entire database would only be a small
> % size of the sstable.
>
> Since the row tombstones are so compact, that's why I think they are good
> candidates for special handling.
>
> On Tue, Feb 13, 2018 at 5:22 PM, J. D. Jordan 
> wrote:
>
>> Have you taken a look at the new stuff introduced by
>> https://issues.apache.org/jira/browse/CASSANDRA-7019 ?  I think it may
>> go a ways to reducing the need for something complicated like this.
>> Though it is an interesting idea as special handling for bulk deletes.
>> If they were truly just sstables that only contained deletes the logic from
>> 7109 would probably go a long ways. Though if you are bulk inserting
>> deletes that is what you would end up with, so maybe it already works.
>>
>> -Jeremiah
>>
>> > On Feb 13, 2018, at 6:04 PM, Jeff Jirsa  wrote:
>> >
>> > On Tue, Feb 13, 2018 at 2:38 PM, Carl Mueller <
>> carl.muel...@smartthings.com>
>> > wrote:
>> >
>> >> In process of doing my second major data purge from a cassandra system.
>> >>
>> >> Almost all of my purging is done via row tombstones. While performing
>> this
>> >> the second time while trying to cajole compaction to occur (in 2.1.x,
>> >> LevelledCompaction) to goddamn actually compact the data, I've been
>> >> thinking as to why there isn't a separate set of sstable infrastructure
>> >> setup for row deletion tombstones.
>> >>
>> >> I'm imagining that row tombstones are written to separate sstables than
>> >> mainline data updates/appends and range/column tombstones.
>> >>
>> >> By writing them to separate sstables, the compaction systems can
>> >> preferentially merge / process them when compacting sstables.
>> >>
>> >> This would create an additional sstable for lookup in the bloom
>> filters,
>> >> granted. I had visions of short circuiting the lookups to other
>> sstables if
>> >> a row tombstone was present in one of the special row tombstone
>> sstables.
>> >>
>> >>
>> > All of the above sounds really interesting to me, but I suspect it's a
>> LOT
>> > of work to make it happen correctly.
>> >
>> > You'd almost end up with 2 sets of logs for the LSM - a tombstone
>> > log/generation, and a data log/generation, and the tombstone logs would
>> be
>> > read-only inputs to data compactions.
>> >
>> >
>> >> But that would only be possible if there was the notion of a "super row
>> >> tombstone" that permanently deleted a rowkey and all future writes
>> would be
>> >> invalidated. Kind of like how a tombstone with a mistakenly huge
>> timestamp
>> >> becomes a sneaky permanent tombstone, but intended. There could be a
>> >> special operation / statement to undo this permanent tombstone, and
>> since
>> >> the row tombstones would be in their own dedicated sstables, they could
>> >> process and compact more quickly, with prioritization by the compactor.
>> >>
>> >>
>> > This part sounds way less interesting to me (other than the fact you can
>> > already do this with a timestamp in the future, but it'll gc away at
>> gcgs).
>> >
>> >
>> >> I'm thinking there must be something I am forgetting in the
>> >> read/write/compaction paths that invalidate this.
>> >>
>> >
>> > There are a lot of places where we do "smart" things to make sure we
>> don't
>> > accidentally resurrect data. Read path includes old sstables for
>> tombstones
>> > for example. Those all need to be concretely identified and handled (and
>> > tested),.
>>
>
>

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

[Michael Kjellman]

i looked at this a few weeks back. this is asf jenkins right? if so, it’s a 
permissions issue on the build executors 

> On Feb 14, 2018, at 9:40 AM, Michael Shuler  wrote:
> 
> Thanks for the feedback on 3.0.16 tentative release.
> 
> Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test
> (in both standard and -compression suites) in CI for me. This test has
> failed 20 times in the last 20 runs. Test output attached.
> 
> Do we wish to fix this before the next cut, since we're here? :)
> 
> -- 
> Kind regards,
> Michael
> 
>> On 02/14/2018 07:30 AM, Jason Brown wrote:
>> I think we can attempt another build and vote now.
>> 
>>> On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown  wrote:
>>> 
>>> CASSANDRA-14219 is committed and tests look clean (https://circleci.com/
>>> workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f).
>>> 
>>> On Tue, Feb 13, 2018 at 1:47 PM, Brandon Williams 
>>> wrote:
>>> 
 I change my vote to -1 binding as well.
 
 On Tue, Feb 13, 2018 at 3:43 PM, Jason Brown 
 wrote:
 
> -1, binding. Unit tests are broken:
> https://circleci.com/gh/jasobrown/cassandra/451#tests/containers/50
> 
> Dave ninja-committed 7df36056b12a13b60097b7a9a4f8155a1d02ff62 to update
> some logging messages, which broke ViewComplexTest. The errors like
 this:
> 
> junit.framework.AssertionFailedError: Expected error message to contain
> 'Cannot drop column a on base table with materialized views', but got
> 'Cannot drop column a on base table table_21 with materialized views.'
> 
> Dave has a followup commit, 40148a178bd9b74b731591aa46b4158efb16b742,
> which
> fixed a few of the errors, but there are four outstanding failures. I
> created CASSANDRA-14219 last week, and assigned it to Dave, but he might
> have missed the notification. Dinesh Joshi has a patch that I will
 review
> ASAP.
> 
> Michael, is there a link of where you ran the tests? If so, can you
 include
> it in the future [VOTE] emails?
> 
> Thanks,
> 
> -Jason
> 
> 
> 
>> On Tue, Feb 13, 2018 at 11:03 AM, Jon Haddad  wrote:
>> 
>> +1
>> 
>>> On Feb 13, 2018, at 10:52 AM, Josh McKenzie 
>> wrote:
>>> 
>>> +1
>>> 
>>> On Feb 13, 2018 9:20 AM, "Marcus Eriksson" 
 wrote:
>>> 
 +1
 
 On Tue, Feb 13, 2018 at 1:29 PM, Aleksey Yeshchenko <
> alek...@apple.com>
 wrote:
 
> +1
> 
> —
> AY
> 
> On 12 February 2018 at 20:31:23, Michael Shuler (
>> mich...@pbandjelly.org)
> wrote:
> 
> I propose the following artifacts for release as 3.0.16.
> 
> sha1: 91e83c72de109521074b14a8eeae1309c3b1f215
> Git:
> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
> shortlog;h=refs/tags/3.0.16-tentative
> Artifacts:
> https://repository.apache.org/content/repositories/
> orgapachecassandra-1154/org/apache/cassandra/apache-
> cassandra/3.0.16/
> Staging repository:
> https://repository.apache.org/content/repositories/
> orgapachecassandra-1154/
> 
> Debian and RPM packages are available here:
> http://people.apache.org/~mshuler
> 
> *** This release addresses an important fix for CASSANDRA-14092
 ***
> "Max ttl of 20 years will overflow localDeletionTime"
> https://issues.apache.org/jira/browse/CASSANDRA-14092
> 
> The vote will be open for 72 hours (longer if needed).
> 
> [1]: (CHANGES.txt) https://goo.gl/rLj59Z
> [2]: (NEWS.txt) https://goo.gl/EkrT4G
> 
> 
 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>> For additional commands, e-mail: dev-h...@cassandra.apache.org
>> 
>> 
> 
 
>>> 
>>> 
>> 
> 
> <3.0-890f319-testall-failure.txt>
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE FAILED] Release Apache Cassandra 3.0.16

[Jason Brown]

Hi Michael,

Which CI environment? iirc, I had several clean runs in circleci with the
latest commits (will run again today).

Thanks,

-Jasoin

On Wed, Feb 14, 2018 at 9:40 AM, Michael Shuler 
wrote:

> Thanks for the feedback on 3.0.16 tentative release.
>
> Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test
> (in both standard and -compression suites) in CI for me. This test has
> failed 20 times in the last 20 runs. Test output attached.
>
> Do we wish to fix this before the next cut, since we're here? :)
>
> --
> Kind regards,
> Michael
>
> On 02/14/2018 07:30 AM, Jason Brown wrote:
> > I think we can attempt another build and vote now.
> >
> > On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown 
> wrote:
> >
> >> CASSANDRA-14219 is committed and tests look clean (
> https://circleci.com/
> >> workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f).
> >>
> >> On Tue, Feb 13, 2018 at 1:47 PM, Brandon Williams 
> >> wrote:
> >>
> >>> I change my vote to -1 binding as well.
> >>>
> >>> On Tue, Feb 13, 2018 at 3:43 PM, Jason Brown 
> >>> wrote:
> >>>
>  -1, binding. Unit tests are broken:
>  https://circleci.com/gh/jasobrown/cassandra/451#tests/containers/50
> 
>  Dave ninja-committed 7df36056b12a13b60097b7a9a4f8155a1d02ff62 to
> update
>  some logging messages, which broke ViewComplexTest. The errors like
> >>> this:
> 
>  junit.framework.AssertionFailedError: Expected error message to
> contain
>  'Cannot drop column a on base table with materialized views', but got
>  'Cannot drop column a on base table table_21 with materialized views.'
> 
>  Dave has a followup commit, 40148a178bd9b74b731591aa46b4158efb16b742,
>  which
>  fixed a few of the errors, but there are four outstanding failures. I
>  created CASSANDRA-14219 last week, and assigned it to Dave, but he
> might
>  have missed the notification. Dinesh Joshi has a patch that I will
> >>> review
>  ASAP.
> 
>  Michael, is there a link of where you ran the tests? If so, can you
> >>> include
>  it in the future [VOTE] emails?
> 
>  Thanks,
> 
>  -Jason
> 
> 
> 
>  On Tue, Feb 13, 2018 at 11:03 AM, Jon Haddad 
> wrote:
> 
> > +1
> >
> >> On Feb 13, 2018, at 10:52 AM, Josh McKenzie 
> > wrote:
> >>
> >> +1
> >>
> >> On Feb 13, 2018 9:20 AM, "Marcus Eriksson" 
> >>> wrote:
> >>
> >>> +1
> >>>
> >>> On Tue, Feb 13, 2018 at 1:29 PM, Aleksey Yeshchenko <
>  alek...@apple.com>
> >>> wrote:
> >>>
>  +1
> 
>  —
>  AY
> 
>  On 12 February 2018 at 20:31:23, Michael Shuler (
> > mich...@pbandjelly.org)
>  wrote:
> 
>  I propose the following artifacts for release as 3.0.16.
> 
>  sha1: 91e83c72de109521074b14a8eeae1309c3b1f215
>  Git:
>  http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
>  shortlog;h=refs/tags/3.0.16-tentative
>  Artifacts:
>  https://repository.apache.org/content/repositories/
>  orgapachecassandra-1154/org/apache/cassandra/apache-
>  cassandra/3.0.16/
>  Staging repository:
>  https://repository.apache.org/content/repositories/
>  orgapachecassandra-1154/
> 
>  Debian and RPM packages are available here:
>  http://people.apache.org/~mshuler
> 
>  *** This release addresses an important fix for CASSANDRA-14092
> >>> ***
>  "Max ttl of 20 years will overflow localDeletionTime"
>  https://issues.apache.org/jira/browse/CASSANDRA-14092
> 
>  The vote will be open for 72 hours (longer if needed).
> 
>  [1]: (CHANGES.txt) https://goo.gl/rLj59Z
>  [2]: (NEWS.txt) https://goo.gl/EkrT4G
> 
> 
> >>>
> >
> >
> > 
> -
> > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> > For additional commands, e-mail: dev-h...@cassandra.apache.org
> >
> >
> 
> >>>
> >>
> >>
> >
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>

[VOTE FAILED] Release Apache Cassandra 3.0.16

[Michael Shuler]

Thanks for the feedback on 3.0.16 tentative release.

Commit 890f319 (current cassandra-3.0 branch HEAD) fails only one test
(in both standard and -compression suites) in CI for me. This test has
failed 20 times in the last 20 runs. Test output attached.

Do we wish to fix this before the next cut, since we're here? :)

-- 
Kind regards,
Michael

On 02/14/2018 07:30 AM, Jason Brown wrote:
> I think we can attempt another build and vote now.
> 
> On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown  wrote:
> 
>> CASSANDRA-14219 is committed and tests look clean (https://circleci.com/
>> workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f).
>>
>> On Tue, Feb 13, 2018 at 1:47 PM, Brandon Williams 
>> wrote:
>>
>>> I change my vote to -1 binding as well.
>>>
>>> On Tue, Feb 13, 2018 at 3:43 PM, Jason Brown 
>>> wrote:
>>>
 -1, binding. Unit tests are broken:
 https://circleci.com/gh/jasobrown/cassandra/451#tests/containers/50

 Dave ninja-committed 7df36056b12a13b60097b7a9a4f8155a1d02ff62 to update
 some logging messages, which broke ViewComplexTest. The errors like
>>> this:

 junit.framework.AssertionFailedError: Expected error message to contain
 'Cannot drop column a on base table with materialized views', but got
 'Cannot drop column a on base table table_21 with materialized views.'

 Dave has a followup commit, 40148a178bd9b74b731591aa46b4158efb16b742,
 which
 fixed a few of the errors, but there are four outstanding failures. I
 created CASSANDRA-14219 last week, and assigned it to Dave, but he might
 have missed the notification. Dinesh Joshi has a patch that I will
>>> review
 ASAP.

 Michael, is there a link of where you ran the tests? If so, can you
>>> include
 it in the future [VOTE] emails?

 Thanks,

 -Jason



 On Tue, Feb 13, 2018 at 11:03 AM, Jon Haddad  wrote:

> +1
>
>> On Feb 13, 2018, at 10:52 AM, Josh McKenzie 
> wrote:
>>
>> +1
>>
>> On Feb 13, 2018 9:20 AM, "Marcus Eriksson" 
>>> wrote:
>>
>>> +1
>>>
>>> On Tue, Feb 13, 2018 at 1:29 PM, Aleksey Yeshchenko <
 alek...@apple.com>
>>> wrote:
>>>
 +1

 —
 AY

 On 12 February 2018 at 20:31:23, Michael Shuler (
> mich...@pbandjelly.org)
 wrote:

 I propose the following artifacts for release as 3.0.16.

 sha1: 91e83c72de109521074b14a8eeae1309c3b1f215
 Git:
 http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
 shortlog;h=refs/tags/3.0.16-tentative
 Artifacts:
 https://repository.apache.org/content/repositories/
 orgapachecassandra-1154/org/apache/cassandra/apache-
 cassandra/3.0.16/
 Staging repository:
 https://repository.apache.org/content/repositories/
 orgapachecassandra-1154/

 Debian and RPM packages are available here:
 http://people.apache.org/~mshuler

 *** This release addresses an important fix for CASSANDRA-14092
>>> ***
 "Max ttl of 20 years will overflow localDeletionTime"
 https://issues.apache.org/jira/browse/CASSANDRA-14092

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

 [1]: (CHANGES.txt) https://goo.gl/rLj59Z
 [2]: (NEWS.txt) https://goo.gl/EkrT4G


>>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
> For additional commands, e-mail: dev-h...@cassandra.apache.org
>
>

>>>
>>
>>
> 

Failed
org.apache.cassandra.db.commitlog.CommitLogSegmentBackpressureTest.testCompressedCommitLogBackpressure

Error Message
Connection refused (Connection refused)

Stacktrace
java.net.ConnectException: Connection refused (Connection refused)
at java.net.PlainSocketImpl.socketConnect(Native Method)
at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
at java.net.Socket.connect(Socket.java:589)
at java.net.Socket.connect(Socket.java:538)
at java.net.Socket.(Socket.java:434)
at java.net.Socket.(Socket.java:211)
at org.jboss.byteman.agent.submit.Submit$Comm.(Submit.java:881)
at org.jboss.byteman.agent.submit.Submit.submitRequest(Submit.java:787)
at org.jboss.byteman.agent.submit.Submit.deleteScripts(Submit.java:697)
at org.jboss.byteman.contrib.bmunit.BMUnit.unloadScriptText(BMUnit.java:295)
at 

[VOTE FAILED] (Take 2) Release Apache Cassandra 3.11.2

[Michael Shuler]

Thanks for all the feedback on this tentative release commit.

Commit 1d506f9 (current cassandra-3.11 branch HEAD) just passed testall
100% for me in CI, so I'll get a new artifact set up soon for Take 3.

-- 
Warm regards,
Mcihael

On 02/14/2018 07:30 AM, Jason Brown wrote:
> CASSANDRA-14234 (which fixes ReadCommandTest) is now committed. I think we
> can attempt another build and vote.
> 
> Thanks,
> 
> -Jason
> 
> On Tue, Feb 13, 2018 at 6:16 PM, Jason Brown  wrote:
> 
>> Thank you, Kurt. I'll get to it within the next 12-24 hours (kids'
>> homework time in the U.S. now ;) )
>>
>> -Jason
>>
>> On Tue, Feb 13, 2018 at 5:10 PM, kurt greaves 
>> wrote:
>>
>>> CASSANDRA-14234 
>>> patch
>>> in for ReadCommandTest if anyone wants to take a look.
>>>
>>> On 14 February 2018 at 00:45, kurt greaves  wrote:
>>>
 ​ReadCommandTest is still not passing. I would be a happy maintainer if
> someone could step up and analyze and contribute a patch; I will
>>> review.


 Having a look. Appears to be just a case of using the same CF for
>>> multiple
 tests and metrics (tombstone histograms) aren't cleared in between.

>>>
>>
>>
> 


-
To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
For additional commands, e-mail: dev-h...@cassandra.apache.org

Apache EU Roadshow CFP Closing Soon (23 February)

[Sharan F]

Hello Everyone

This is an initial reminder to let you all know that we are holding an 
Apache EU Roadshow co-located with FOSS Backstage in Berlin on 13^th and 
14^th June 2018. https://s.apache.org/tCHx


The Call for Proposals (CFP) for the Apache EU Roadshow is currently 
open and will close at the end of next week, so if you have been 
delaying making a submission because the closing date seemed a long way 
off, then it's time to start getting your proposals submitted.


So what are we looking for?
We will have 2 Apache Devrooms available during the 2 day Roadshow so 
are looking for projects including incubating ones, to submit 
presentations, panel discussions, BoFs, or workshop proposals. The main 
focus of the Roadshow will be IoT, Cloud, Httpd and Tomcat so if your 
project is involved in or around any of these technologies at Apache 
then we are very interested in hearing from you.


Community and collaboration is important at Apache so if your project is 
interested in organising a project sprint, meetup or hackathon during 
the Roadshow, then please submit it inthe CFP as we do have some space 
available to allocate for these.


If you are wanting to submit a talk on open source community related 
topics such as the Apache Way, governance or legal aspects then please 
submit these to the CFP for FOSS Backstage.


Tickets for the Apache EU Roadshow are included as part of the 
registration for FOSS Backstage, so to attend the Roadshow you will need 
to register for FOSS Backstage. Early Bird tickets are still available 
until the 21^st February 2018.


Please see below for important URLs to remember:

-  To submit a CFP for the Apache EU Roadshow 
:http://apachecon.com/euroadshow18/ 


-  To submit a CFP for FOSS Backstage : 
https://foss-backstage.de/call-papers


-  To register to attend the Apache EU Roadshow and/or FOSS Backstage : 
https://foss-backstage.de/tickets


For further updates and information about the Apache EU Roadshowplease 
check http://apachecon.com/euroadshow18/


Thanks
Sharan Foga, VP Apache Community Development

Re: [VOTE] Release Apache Cassandra 3.0.16

[Jason Brown]

I think we can attempt another build and vote now.

On Tue, Feb 13, 2018 at 3:44 PM, Jason Brown  wrote:

> CASSANDRA-14219 is committed and tests look clean (https://circleci.com/
> workflow-run/d0a2622a-e74f-4c46-b0ad-a84ca063736f).
>
> On Tue, Feb 13, 2018 at 1:47 PM, Brandon Williams 
> wrote:
>
>> I change my vote to -1 binding as well.
>>
>> On Tue, Feb 13, 2018 at 3:43 PM, Jason Brown 
>> wrote:
>>
>> > -1, binding. Unit tests are broken:
>> > https://circleci.com/gh/jasobrown/cassandra/451#tests/containers/50
>> >
>> > Dave ninja-committed 7df36056b12a13b60097b7a9a4f8155a1d02ff62 to update
>> > some logging messages, which broke ViewComplexTest. The errors like
>> this:
>> >
>> > junit.framework.AssertionFailedError: Expected error message to contain
>> > 'Cannot drop column a on base table with materialized views', but got
>> > 'Cannot drop column a on base table table_21 with materialized views.'
>> >
>> > Dave has a followup commit, 40148a178bd9b74b731591aa46b4158efb16b742,
>> > which
>> > fixed a few of the errors, but there are four outstanding failures. I
>> > created CASSANDRA-14219 last week, and assigned it to Dave, but he might
>> > have missed the notification. Dinesh Joshi has a patch that I will
>> review
>> > ASAP.
>> >
>> > Michael, is there a link of where you ran the tests? If so, can you
>> include
>> > it in the future [VOTE] emails?
>> >
>> > Thanks,
>> >
>> > -Jason
>> >
>> >
>> >
>> > On Tue, Feb 13, 2018 at 11:03 AM, Jon Haddad  wrote:
>> >
>> > > +1
>> > >
>> > > > On Feb 13, 2018, at 10:52 AM, Josh McKenzie 
>> > > wrote:
>> > > >
>> > > > +1
>> > > >
>> > > > On Feb 13, 2018 9:20 AM, "Marcus Eriksson" 
>> wrote:
>> > > >
>> > > >> +1
>> > > >>
>> > > >> On Tue, Feb 13, 2018 at 1:29 PM, Aleksey Yeshchenko <
>> > alek...@apple.com>
>> > > >> wrote:
>> > > >>
>> > > >>> +1
>> > > >>>
>> > > >>> —
>> > > >>> AY
>> > > >>>
>> > > >>> On 12 February 2018 at 20:31:23, Michael Shuler (
>> > > mich...@pbandjelly.org)
>> > > >>> wrote:
>> > > >>>
>> > > >>> I propose the following artifacts for release as 3.0.16.
>> > > >>>
>> > > >>> sha1: 91e83c72de109521074b14a8eeae1309c3b1f215
>> > > >>> Git:
>> > > >>> http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=
>> > > >>> shortlog;h=refs/tags/3.0.16-tentative
>> > > >>> Artifacts:
>> > > >>> https://repository.apache.org/content/repositories/
>> > > >>> orgapachecassandra-1154/org/apache/cassandra/apache-
>> > cassandra/3.0.16/
>> > > >>> Staging repository:
>> > > >>> https://repository.apache.org/content/repositories/
>> > > >>> orgapachecassandra-1154/
>> > > >>>
>> > > >>> Debian and RPM packages are available here:
>> > > >>> http://people.apache.org/~mshuler
>> > > >>>
>> > > >>> *** This release addresses an important fix for CASSANDRA-14092
>> ***
>> > > >>> "Max ttl of 20 years will overflow localDeletionTime"
>> > > >>> https://issues.apache.org/jira/browse/CASSANDRA-14092
>> > > >>>
>> > > >>> The vote will be open for 72 hours (longer if needed).
>> > > >>>
>> > > >>> [1]: (CHANGES.txt) https://goo.gl/rLj59Z
>> > > >>> [2]: (NEWS.txt) https://goo.gl/EkrT4G
>> > > >>>
>> > > >>>
>> > > >>
>> > >
>> > >
>> > > -
>> > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org
>> > > For additional commands, e-mail: dev-h...@cassandra.apache.org
>> > >
>> > >
>> >
>>
>
>

Re: [VOTE] (Take 2) Release Apache Cassandra 3.11.2

[Jason Brown]

CASSANDRA-14234 (which fixes ReadCommandTest) is now committed. I think we
can attempt another build and vote.

Thanks,

-Jason

On Tue, Feb 13, 2018 at 6:16 PM, Jason Brown  wrote:

> Thank you, Kurt. I'll get to it within the next 12-24 hours (kids'
> homework time in the U.S. now ;) )
>
> -Jason
>
> On Tue, Feb 13, 2018 at 5:10 PM, kurt greaves 
> wrote:
>
>> CASSANDRA-14234 
>> patch
>> in for ReadCommandTest if anyone wants to take a look.
>>
>> On 14 February 2018 at 00:45, kurt greaves  wrote:
>>
>> > ​ReadCommandTest is still not passing. I would be a happy maintainer if
>> >> someone could step up and analyze and contribute a patch; I will
>> review.
>> >
>> >
>> > Having a look. Appears to be just a case of using the same CF for
>> multiple
>> > tests and metrics (tombstone histograms) aren't cleared in between.
>> >
>>
>
>