Re: [VOTE] Release Apache Cassandra 3.11.16 - SECOND ATTEMPT

[Tommy Stendahl via dev]

+1 nb

-Original Message-
From: Brandon Williams 
mailto:brandon%20williams%20%3cdri...@gmail.com%3e>>
Reply-To: dev@cassandra.apache.org
To: dev@cassandra.apache.org
Subject: Re: [VOTE] Release Apache Cassandra 3.11.16 - SECOND ATTEMPT
Date: Wed, 16 Aug 2023 12:18:19 -0500


+1


Kind Regards,

Brandon


On Tue, Aug 15, 2023 at 12:53 PM Miklosovic, Stefan

<



stefan.mikloso...@netapp.com

> wrote:


This is the second attempt to pass the vote after [1] is fixed.


Proposing the test build of Cassandra 3.11.16 for release.


sha1: 681b6ca103d91d940a9fecb8cd812f58dd2490d0

Git:



https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-41f531def243a377=1=7ec16b78-673c-4f06-a279-458e1ec0bb39=https%3A%2F%2Fgithub.com%2Fapache%2Fcassandra%2Ftree%2F3.11.16-tentative


Maven Artifacts:



https://repository.apache.org/content/repositories/orgapachecassandra-1306/org/apache/cassandra/cassandra-all/3.11.16/



The Source and Build Artifacts, and the Debian and RPM packages and 
repositories, are available here:



https://dist.apache.org/repos/dist/dev/cassandra/3.11.16/



The vote will be open for 72 hours (longer if needed). Everyone who has tested 
the build is invited to vote. Votes by PMC members are considered binding. A 
vote passes if there are at least three binding +1s and no -1's.


[1]:



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


[2]: CHANGES.txt:



https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-bd326a3ed418c507=1=7ec16b78-673c-4f06-a279-458e1ec0bb39=https%3A%2F%2Fgithub.com%2Fapache%2Fcassandra%2Fblob%2F3.11.16-tentative%2FCHANGES.txt


[3]: NEWS.txt:



https://protect2.fireeye.com/v1/url?k=31323334-501d5122-313273af-45444731-bad122fcfa269241=1=7ec16b78-673c-4f06-a279-458e1ec0bb39=https%3A%2F%2Fgithub.com%2Fapache%2Fcassandra%2Fblob%2F3.11.16-tentative%2FNEWS.txt

Re: [VOTE] Release dtest-api 0.0.16

[Brandon Williams]

+1

Kind Regards,
Brandon

On Wed, Aug 16, 2023 at 4:34 PM Dinesh Joshi  wrote:
>
> Proposing the test build of in-jvm dtest API 0.0.16 for release.
>
> Repository:
> https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git
>
> Candidate SHA:
> https://github.com/apache/cassandra-in-jvm-dtest-api/commit/1ba6ef93d0721741b5f6d6d72cba3da03fe78438
> tagged with 0.0.16
>
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1307/org/apache/cassandra/dtest-api/0.0.16/
>
> Key signature: 53371F9B1B425A336988B6A03B6042413D323470
>
> Changes since last release:
>
> * CASSANDRA-18727 - JMXUtil.getJmxConnector should retry connection attempts
>
> The vote will be open for 24 hours. Everyone who has tested the build
> is invited to vote. Votes by PMC members are considered binding. A
> vote passes if there are at least three binding +1s.
>

Re: [VOTE] Release dtest-api 0.0.16

[Francisco Guerrero]

+1 (nb), thank you!

On 2023/08/16 22:23:52 Doug Rohrer wrote:
> +1 (nb) - Thanks Dinesh!
> 
> Doug
> 
> > On Aug 16, 2023, at 5:34 PM, Dinesh Joshi  wrote:
> > 
> > Proposing the test build of in-jvm dtest API 0.0.16 for release.
> > 
> > Repository:
> > https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git
> > 
> > Candidate SHA:
> > https://github.com/apache/cassandra-in-jvm-dtest-api/commit/1ba6ef93d0721741b5f6d6d72cba3da03fe78438
> > tagged with 0.0.16
> > 
> > Artifacts:
> > https://repository.apache.org/content/repositories/orgapachecassandra-1307/org/apache/cassandra/dtest-api/0.0.16/
> > 
> > Key signature: 53371F9B1B425A336988B6A03B6042413D323470
> > 
> > Changes since last release:
> > 
> > * CASSANDRA-18727 - JMXUtil.getJmxConnector should retry connection attempts
> > 
> > The vote will be open for 24 hours. Everyone who has tested the build
> > is invited to vote. Votes by PMC members are considered binding. A
> > vote passes if there are at least three binding +1s.
> > 
> 
> 

Re: [DISCUSS] CASSANDRA-18743 Deprecation of metrics-reporter-config

[Doug Rohrer]

My only concern about removal in 5.1 would be that removing it in a “minor” 
release would really be a breaking change, and semver says that should happen 
in a major version.

If we really want to be semver compliant, it shouldn’t be removed until 6.0 
(or, if we remove it in the next release, we should call that 6.0, but that 
conflicts with the idea of a “yearly major” so I’m not sure where we land at 
the end of the day).

Doug

> On Aug 16, 2023, at 4:14 PM, Abe Ratnofsky  wrote:
> 
> There's consensus here to deprecate metrics-reporter-config in 5.0.
> 
> Is there any objection to removing it in 5.1?
> 
>> On Aug 11, 2023, at 10:01 AM, Maxim Muzafarov  wrote:
>> 
>> +1
>> 
>> The rationale for deprecating/removing this library is not just that
>> it is obsolete and doesn't get updates. In fact, when the
>> metrics-reporter-config [1] was added the dropwizard metrics library
>> (formerly com.yammer.metrics [2]) didn't support exporting metrics to
>> files like csv, so it made sense at that time. Now it is fully covered
>> by the drowpwizrd reporters [3], so users can achieve the same
>> behaviour without the need for metrics-reporter-config. And that's why
>> I have a lot of doubts about it being used by anyone, but deprecation
>> is friendlier because there's no rush to remove it. :-)
>> 
>> 
>> [1] https://issues.apache.org/jira/browse/CASSANDRA-4430
>> [2] https://issues.apache.org/jira/browse/CASSANDRA-5838
>> [3] https://metrics.dropwizard.io/4.2.0/getting-started.html#other-reporting
>> 
>> On Fri, 11 Aug 2023 at 16:50, Caleb Rackliffe  
>> wrote:
>>> 
>>> +1
>>> 
 On Aug 11, 2023, at 8:10 AM, Brandon Williams  wrote:
 
 +1
 
 Kind Regards,
 Brandon
 
> On Fri, Aug 11, 2023 at 8:08 AM Ekaterina Dimitrova
>  wrote:
> 
> 
> “ The rationale for this proposed deprecation is that the upcoming 5.0 
> release is a good time to evaluate dependencies that are no longer 
> receiving updates and will become risks in the future.”
> 
> Thank you for raising it, I support your proposal for deprecation
> 
>> On Fri, 11 Aug 2023 at 8:55, Abe Ratnofsky  wrote:
>> 
>> Hey folks,
>> 
>> Opening a thread to get input on a proposed dependency deprecation in 
>> 5.0: metrics-reporter-config has been archived for 3 years and not 
>> updated in nearly 6 years.
>> 
>> This project has a minor security issue with its usage of unsafe YAML 
>> loading via snakeyaml’s unprotected Constructor: 
>> https://nvd.nist.gov/vuln/detail/CVE-2022-1471
>> 
>> This CVE is reasonable to suppress, since operators should be able to 
>> trust their YAML configuration files.
>> 
>> The rationale for this proposed deprecation is that the upcoming 5.0 
>> release is a good time to evaluate dependencies that are no longer 
>> receiving updates and will become risks in the future.
>> 
>> https://issues.apache.org/jira/browse/CASSANDRA-18743
>> 
>> —
>> Abe
>> 
> 

Re: [VOTE] Release dtest-api 0.0.16

[Doug Rohrer]

+1 (nb) - Thanks Dinesh!

Doug

> On Aug 16, 2023, at 5:34 PM, Dinesh Joshi  wrote:
> 
> Proposing the test build of in-jvm dtest API 0.0.16 for release.
> 
> Repository:
> https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git
> 
> Candidate SHA:
> https://github.com/apache/cassandra-in-jvm-dtest-api/commit/1ba6ef93d0721741b5f6d6d72cba3da03fe78438
> tagged with 0.0.16
> 
> Artifacts:
> https://repository.apache.org/content/repositories/orgapachecassandra-1307/org/apache/cassandra/dtest-api/0.0.16/
> 
> Key signature: 53371F9B1B425A336988B6A03B6042413D323470
> 
> Changes since last release:
> 
> * CASSANDRA-18727 - JMXUtil.getJmxConnector should retry connection attempts
> 
> The vote will be open for 24 hours. Everyone who has tested the build
> is invited to vote. Votes by PMC members are considered binding. A
> vote passes if there are at least three binding +1s.
> 

[VOTE] Release dtest-api 0.0.16

[Dinesh Joshi]

Proposing the test build of in-jvm dtest API 0.0.16 for release.

Repository:
https://gitbox.apache.org/repos/asf?p=cassandra-in-jvm-dtest-api.git

Candidate SHA:
https://github.com/apache/cassandra-in-jvm-dtest-api/commit/1ba6ef93d0721741b5f6d6d72cba3da03fe78438
tagged with 0.0.16

Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1307/org/apache/cassandra/dtest-api/0.0.16/

Key signature: 53371F9B1B425A336988B6A03B6042413D323470

Changes since last release:

* CASSANDRA-18727 - JMXUtil.getJmxConnector should retry connection attempts

The vote will be open for 24 hours. Everyone who has tested the build
is invited to vote. Votes by PMC members are considered binding. A
vote passes if there are at least three binding +1s.

[Discuss] Detecting token-ownership mismatch

[Jaydeep Chovatia]

Hi,


As we know, Cassandra exchanges important topology and
token-ownership-related details over Gossip. Cassandra internally maintains
the following two separate caches that have the token-ownership information
maintained: 1) Gossip cache and 2) Storage Service cache. The first Gossip
cache is updated on a node, followed by the storage service cache. In the
hot path, ownership is calculated from the storage service cache. Since two
separate caches maintain the same information, then inconsistencies are
bound to happen. It could be very well feasible that the Gossip cache has
up-to-date ownership of the Cassandra cluster, but the service cache does
not, and in that scenario, inconsistent data will be served to the user.

Currently, there is no mechanism in Cassandra that detects and fixes these
two caches.

*Long-term solution*
We are going with the long-term transactional metadata (
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-21) to handle
such inconsistencies, and that’s the right thing to do.

*Short-term solution*
But CEP-21 might take some time, and until then, there is a need to
*detect* such
inconsistencies. Once we detect inconsistencies, then we could have two
options: 1) restart the node or 2) Fix the inconsistencies on-the-fly.

I've created the following JIRA for the short-term fix:
https://issues.apache.org/jira/browse/CASSANDRA-18758


Does this sound valuable?


Jaydeep

Re: [VOTE] Release Apache Cassandra 3.11.16 - SECOND ATTEMPT

[Maxim Muzafarov]

+1 (nb)

verified checksums, signing, and build from sources.

The link is broken :-(
Maven Artifacts:
https://repository.apache.org/content/repositories/orgapachecassandra-1306/org/apache/cassandra/cassandra-all/3.11.16/

On Wed, 16 Aug 2023 at 19:18, Brandon Williams  wrote:
>
> +1
>
> Kind Regards,
> Brandon
>
> On Tue, Aug 15, 2023 at 12:53 PM Miklosovic, Stefan
>  wrote:
> >
> > This is the second attempt to pass the vote after [1] is fixed.
> >
> > Proposing the test build of Cassandra 3.11.16 for release.
> >
> > sha1: 681b6ca103d91d940a9fecb8cd812f58dd2490d0
> > Git: https://github.com/apache/cassandra/tree/3.11.16-tentative
> > Maven Artifacts: 
> > https://repository.apache.org/content/repositories/orgapachecassandra-1306/org/apache/cassandra/cassandra-all/3.11.16/
> >
> > The Source and Build Artifacts, and the Debian and RPM packages and 
> > repositories, are available here: 
> > https://dist.apache.org/repos/dist/dev/cassandra/3.11.16/
> >
> > The vote will be open for 72 hours (longer if needed). Everyone who has 
> > tested the build is invited to vote. Votes by PMC members are considered 
> > binding. A vote passes if there are at least three binding +1s and no -1's.
> >
> > [1]: https://issues.apache.org/jira/browse/CASSANDRA-18751
> > [2]: CHANGES.txt: 
> > https://github.com/apache/cassandra/blob/3.11.16-tentative/CHANGES.txt
> > [3]: NEWS.txt: 
> > https://github.com/apache/cassandra/blob/3.11.16-tentative/NEWS.txt

Re: [DISCUSS] CASSANDRA-18743 Deprecation of metrics-reporter-config

[Abe Ratnofsky]

There's consensus here to deprecate metrics-reporter-config in 5.0.

Is there any objection to removing it in 5.1?

> On Aug 11, 2023, at 10:01 AM, Maxim Muzafarov  wrote:
> 
> +1
> 
> The rationale for deprecating/removing this library is not just that
> it is obsolete and doesn't get updates. In fact, when the
> metrics-reporter-config [1] was added the dropwizard metrics library
> (formerly com.yammer.metrics [2]) didn't support exporting metrics to
> files like csv, so it made sense at that time. Now it is fully covered
> by the drowpwizrd reporters [3], so users can achieve the same
> behaviour without the need for metrics-reporter-config. And that's why
> I have a lot of doubts about it being used by anyone, but deprecation
> is friendlier because there's no rush to remove it. :-)
> 
> 
> [1] https://issues.apache.org/jira/browse/CASSANDRA-4430
> [2] https://issues.apache.org/jira/browse/CASSANDRA-5838
> [3] https://metrics.dropwizard.io/4.2.0/getting-started.html#other-reporting
> 
> On Fri, 11 Aug 2023 at 16:50, Caleb Rackliffe  
> wrote:
>> 
>> +1
>> 
>>> On Aug 11, 2023, at 8:10 AM, Brandon Williams  wrote:
>>> 
>>> +1
>>> 
>>> Kind Regards,
>>> Brandon
>>> 
 On Fri, Aug 11, 2023 at 8:08 AM Ekaterina Dimitrova
  wrote:
 
 
 “ The rationale for this proposed deprecation is that the upcoming 5.0 
 release is a good time to evaluate dependencies that are no longer 
 receiving updates and will become risks in the future.”
 
 Thank you for raising it, I support your proposal for deprecation
 
> On Fri, 11 Aug 2023 at 8:55, Abe Ratnofsky  wrote:
> 
> Hey folks,
> 
> Opening a thread to get input on a proposed dependency deprecation in 
> 5.0: metrics-reporter-config has been archived for 3 years and not 
> updated in nearly 6 years.
> 
> This project has a minor security issue with its usage of unsafe YAML 
> loading via snakeyaml’s unprotected Constructor: 
> https://nvd.nist.gov/vuln/detail/CVE-2022-1471
> 
> This CVE is reasonable to suppress, since operators should be able to 
> trust their YAML configuration files.
> 
> The rationale for this proposed deprecation is that the upcoming 5.0 
> release is a good time to evaluate dependencies that are no longer 
> receiving updates and will become risks in the future.
> 
> https://issues.apache.org/jira/browse/CASSANDRA-18743
> 
> —
> Abe
> 

Re: [VOTE] Release Apache Cassandra 3.11.16 - SECOND ATTEMPT

[Brandon Williams]

+1

Kind Regards,
Brandon

On Tue, Aug 15, 2023 at 12:53 PM Miklosovic, Stefan
 wrote:
>
> This is the second attempt to pass the vote after [1] is fixed.
>
> Proposing the test build of Cassandra 3.11.16 for release.
>
> sha1: 681b6ca103d91d940a9fecb8cd812f58dd2490d0
> Git: https://github.com/apache/cassandra/tree/3.11.16-tentative
> Maven Artifacts: 
> https://repository.apache.org/content/repositories/orgapachecassandra-1306/org/apache/cassandra/cassandra-all/3.11.16/
>
> The Source and Build Artifacts, and the Debian and RPM packages and 
> repositories, are available here: 
> https://dist.apache.org/repos/dist/dev/cassandra/3.11.16/
>
> The vote will be open for 72 hours (longer if needed). Everyone who has 
> tested the build is invited to vote. Votes by PMC members are considered 
> binding. A vote passes if there are at least three binding +1s and no -1's.
>
> [1]: https://issues.apache.org/jira/browse/CASSANDRA-18751
> [2]: CHANGES.txt: 
> https://github.com/apache/cassandra/blob/3.11.16-tentative/CHANGES.txt
> [3]: NEWS.txt: 
> https://github.com/apache/cassandra/blob/3.11.16-tentative/NEWS.txt

Re: [VOTE] Release Apache Cassandra 3.11.16 - SECOND ATTEMPT

[Alex Petrov]

+1

On Tue, Aug 15, 2023, at 7:53 PM, Miklosovic, Stefan wrote:
> This is the second attempt to pass the vote after [1] is fixed.
> 
> Proposing the test build of Cassandra 3.11.16 for release.
> 
> sha1: 681b6ca103d91d940a9fecb8cd812f58dd2490d0
> Git: https://github.com/apache/cassandra/tree/3.11.16-tentative
> Maven Artifacts: 
> https://repository.apache.org/content/repositories/orgapachecassandra-1306/org/apache/cassandra/cassandra-all/3.11.16/
> 
> The Source and Build Artifacts, and the Debian and RPM packages and 
> repositories, are available here: 
> https://dist.apache.org/repos/dist/dev/cassandra/3.11.16/
> 
> The vote will be open for 72 hours (longer if needed). Everyone who has 
> tested the build is invited to vote. Votes by PMC members are considered 
> binding. A vote passes if there are at least three binding +1s and no -1's.
> 
> [1]: https://issues.apache.org/jira/browse/CASSANDRA-18751
> [2]: CHANGES.txt: 
> https://github.com/apache/cassandra/blob/3.11.16-tentative/CHANGES.txt
> [3]: NEWS.txt: 
> https://github.com/apache/cassandra/blob/3.11.16-tentative/NEWS.txt
> 

Re: [VOTE] Release Apache Cassandra 3.11.16 - SECOND ATTEMPT

[Mick Semb Wever]

>
> The vote will be open for 72 hours (longer if needed). Everyone who has
> tested the build is invited to vote. Votes by PMC members are considered
> binding. A vote passes if there are at least three binding +1s and no -1's.
>


+1

Checked
- signing correct
- checksums are correct
- source artefact builds
- binary artefact runs
- debian package runs
- redhat package runs
- debian repo installs and runs
- redhat (almalinux) repo installs and  runs