Re: A proposal to move away from Jira-centric development

I too, use this method quite a bit, almost every single day. On Mon, Aug 15, 2016 at 12:43 PM, Yuki Morishita wrote: > As an active committer, the most important thing for me is to be able > to *look up* design discussion and decision easily later. > > I often look up the git history or CHANGES.

Re: A proposal to move away from Jira-centric development

So will I, if that happens, which has never happened in the last ~7 years. On Mon, Aug 15, 2016 at 4:27 PM, Jeff Jirsa wrote: > > On 8/15/16, 2:15 PM, "Marvin Humphrey" wrote: > > > Julian Hyde, who made the proposal, is active in the Apache Incubator … > >I propose that when a JIRA is crea

Re: Thanks for all the fish.

If there is one thing I am damn sure of, it's that I wouldn't be here without Jonathan's leadership and friendship. Thank you for all you've done, old buddy. Kind Regards, Brandon On Fri, Aug 19, 2016 at 2:20 PM, Michael Kjellman < mkjell...@internalcircle.com> wrote: > Just wanted to say thank

Re: [ANN]: Cert management with self-signed CA for Cassandra (and presumably other Java stuff)

+1 On Aug 22, 2016 9:51 PM, "Eric Evans" wrote: > On Mon, Aug 22, 2016 at 5:28 PM, Jake Farrell wrote: > > Any reason to not include this in the docs/operating or as a utility in > repo > > to make it easier for end users to find all information in one place? > Know > > this has come up on othe

Re: Can we change the number of vnodes on existing nodes?

I am curious exactly what gossip issues you are encountering. On Fri, Sep 9, 2016 at 7:45 PM, Dikang Gu wrote: > Hi, > > We have some big cluster (500+ nodes), they have 256 vnodes on physical > host, which is causing a lot of problems to us, especially make the gossip > to be in-efficient. > >

Re: [VOTE] Release Apache Cassandra 3.0.9

+1 On Thu, Sep 15, 2016 at 1:57 PM, Jake Luciani wrote: > I propose the following artifacts for release as 3.0.9. > > sha1: d600f51ee1a3eb7b30ce3c409129567b70c22012 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.9-tentative > Artifacts: > https://re

Re: [VOTE] Release Apache Cassandra 2.2.8

+1 On Fri, Sep 23, 2016 at 6:04 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.8. > > sha1: e9fe96f404b6a936ac5dbceb8f3934fe0d098a97 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.2.8-tentative > Artifacts: > https://

Re: [VOTE] Release Apache Cassandra 3.8

+1 On Mon, Sep 26, 2016 at 9:52 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.8. > > sha1: ce609d19fd130e16184d9e6d37ffee4a1ebad607 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.8-tentative > Artifacts: > https://repo

Re: [VOTE] Release Apache Cassandra 3.9

+1 On Mon, Sep 26, 2016 at 10:12 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.9. > > sha1: c1fa21458777b51a9b21795330ed6f298103b436 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.9-tentative > Artifacts: > https://rep

Re: [VOTE] Accept dtests Donation Into Project

+1 On Fri, Sep 30, 2016 at 1:51 PM, Nate McCall wrote: > I propose we begin the process of accepting the contribution of the > dtest codebase (https://github.com/riptano/cassandra-dtest) into the > project. > > Background discussion thread here: > https://lists.apache.org/thread.html/840fd900fb7

Re: [VOTE] Release Apache Cassandra 2.1.16

+1 On Oct 5, 2016 6:10 PM, "Michael Shuler" wrote: > I propose the following artifacts for release as 2.1.16. > > sha1: 87034cd05964e64c6c925597279865a40a8c152f > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.1.16-tentative > Artifacts: > https://repos

Re: [VOTE] Release Apache Cassandra 2.1.16

It's too minor for a re-roll, and safe enough to just apply yourself if you want it. On Mon, Oct 10, 2016 at 2:44 PM, Michael Shuler wrote: > Nate, do think CASSANDRA-12758 should go to 2.1.x? > > -- > Michael > > On 10/10/2016 02:26 PM, Nate McCall wrote: > > Hi Romain, > > I appreciate you spe

Re: CASSANDRA-12758 in 2.1? (was: Re: [VOTE] Release Apache Cassandra 2.1.16)

It's simple and very low risk, I wouldn't be adverse to it since 11363 is in 2.1. On Mon, Oct 10, 2016 at 3:55 PM, Michael Shuler wrote: > I also agree this is minor and did not intend to re-roll. > > My question is whether CASSANDRA-12758 should go to to the > 'cassandra-2.1' branch and be tagg

Re: [VOTE] Release Apache Cassandra 3.0.10

+1 On Mon, Oct 31, 2016 at 11:12 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: 817ba038783212b716f6981b26c8348ffdc92f59 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.10-tentative > Artifacts: > https

Re: [VOTE] Release Apache Cassandra 3.10

+1 On Mon, Oct 31, 2016 at 10:18 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: a3828ca8b755fc98799867baf07039f7ff53be05 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.10-tentative > Artifacts: > https://r

Re: Wiki admin

Done. On Mon, Nov 7, 2016 at 9:37 AM, Michael Shuler wrote: > If someone could set the user MichaelShuler as admin, I can help with > user requests, such as the the current request on the list to add > winguzone. > > -- > Michael >

Re: [VOTE] Close client-...@cassandra.apache.org mailing list

As the moderator of this list, +1. It was more helpful in the thrift days (where I built a client, and thus became the moderator) but is practically useless in the cql world. On Sun, Nov 6, 2016 at 11:11 PM, Jeff Jirsa wrote: > There exists a nearly unused mailing list, client-...@cassandra.apa

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

+1 On Tue, Nov 8, 2016 at 2:08 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: 4e0bced5e6a82ebd22b074b8ef96d930c5f3159d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.10-tentative > Artifacts: > https:/

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

+1 On Fri, Nov 11, 2016 at 7:36 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.10. > > sha1: d6a3ef4863142c3f9fc1def911f28341fc78f2e8 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.10-tentative > Artifacts: > https:

Re: Rough roadmap for 4.0

It's not marked fixed, it's marked resolved and the resolution is duplicate. This is how all dupes are marked in jira. On Fri, Nov 18, 2016 at 2:30 PM, Edward Capriolo wrote: > These tickets claim to duplicate each other: > > https://issues.apache.org/jira/browse/CASSANDRA-12674 > https://issue

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

+1 On Fri, Nov 18, 2016 at 12:08 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.10-tentative > Artifacts: > https://r

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

I'll change to binding -1 for the reasons previously listed. On Fri, Nov 18, 2016 at 12:08 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 96d67b109a2ef858c2753bbb9853d01460cb8f8e > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > sh

Re: Where do I find EverywhereStrategy?

Relevant: https://issues.apache.org/jira/browse/CASSANDRA-12912 On Wed, Nov 30, 2016 at 12:32 PM, Jeff Jirsa wrote: > > > On 2016-11-30 10:02 (-0800), Ben Bromhead wrote: > > Also apparently the Everywhere Strategy is a bad idea (tm) according to > > comments in https://issues.apache.org/jira/b

Re: How does a node know it's fully joined to the ring?

Probably want to do something like SystemKeyspace.bootstrapComplete() On Thu, Jan 5, 2017 at 1:58 PM, Eric Stevens wrote: > I'm working on a bug report in my Deleting Compaction Strategy project. > > Some of the provided deletion strategies allow for a series of deletion > rules to be added to a

Re: How does a node know it's fully joined to the ring?

Looking at it, I'm not sure if it's quite the right thing for me. Maybe I > used the wrong terminology; it actually doesn't matter if the node is still > bootstrapping, as long as it could query other nodes in the cluster. > > On Thu, Jan 5, 2017 at 1:03 PM Brandon Willia

Re: Rollback procedure for Cassandra Upgrade.

However, it's good to determine *how* it failed. If nodetool just died or timed out, that's no big deal, it'll finish. On Mon, Jan 9, 2017 at 11:00 PM, Jonathan Haddad wrote: > There's no downgrade procedure. You either upgrade or you go back to a > snapshot from the previous version. > On Mon,

Re: [VOTE] 3.X branch feature freeze

+1 On Fri, Jan 13, 2017 at 11:21 AM, Aleksey Yeschenko wrote: > Hi all! > > It seems like we have a general consensus on ending tick-tock at 3.11, and > moving > on to stabilisation-only for 3.11.x series. > > In light of this, I suggest immediate feature freeze in the 3.X branch. > > Meaning th

Re: [VOTE] Release Apache Cassandra 3.10 (Take 4)

+1 On Fri, Jan 13, 2017 at 6:46 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 9c2ab25556fad06a6a4d58f4bb652719a8a1bc27 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.10-tentative > Artifacts: > https://re

Re: Dropped messages on random nodes.

The lion's share of your drops are from cross-node timeouts, which require clock synchronization, so check that first. If your clocks are synced, that means not only are you showing eager dropping based on time, but despite the eager dropping you are still facing overload. That local, non-gc paus

Re: [VOTE] Release Apache Cassandra 3.10 (Take 5)

+1 On Tue, Jan 31, 2017 at 3:29 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: 3cf415279c171fe20802ad90f181eed7da04c58d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.10-tentative > Artifacts: > https://re

Re: [VOTE] Release Apache Cassandra 2.1.17

+1 On Wed, Feb 15, 2017 at 7:16 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.17. > > sha1: 943db2488c8b62e1fbe03b132102f0e579c9ae17 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.1.17-tentative > Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 3.0.11

+1 On Wed, Feb 15, 2017 at 7:15 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.11. > > sha1: 338226e042a22242645ab54a372c7c1459e78a01 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.11-tentative > Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 2.2.9

+1 On Wed, Feb 15, 2017 at 7:16 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.9. > > sha1: 70a08f1c35091a36f7d9cc4816259210c2185267 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.2.9-tentative > Artifacts: > https://

Re: RemoveNode Behavior Question

Every topology operation tries to respect/restore the RF except for assassinate. On Wed, Feb 22, 2017 at 12:45 PM, Anubhav Kale < anubhav.k...@microsoft.com.invalid> wrote: > Hello, > > Recently, I started noticing an interesting pattern. When I execute > "removenode", a subset of the nodes that

Re: RemoveNode Behavior Question

ovenode only owns partial ranges. > > -Original Message- > From: Brandon Williams [mailto:dri...@gmail.com] > Sent: Wednesday, February 22, 2017 10:49 AM > To: dev@cassandra.apache.org > Subject: Re: RemoveNode Behavior Question > > Every topology operation tries to respec

Re: Consistent vs inconsistent range movements

https://issues.apache.org/jira/browse/CASSANDRA-11610 Disable only if adding single nodes to different DCs or racks. On Fri, Mar 3, 2017 at 5:44 PM, Jeff Jirsa wrote: > Imagine you have a cluster with RF=3, and you write a key with CL:QUORUM, > it goes to nodes 1 and 3, but node 2 is offline. >

Re: [VOTE] Release Apache Cassandra 3.0.12

+1 On Tue, Mar 7, 2017 at 10:15 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.12. > > This release addresses a possible 2.1->3.0 upgrade issue[3], along with > a few fixes committed since 3.0.11. > > sha1: 50560aaf0f2d395271ade59ba9b900a84cae70f1 > Git: > http:

Re: Testing and jira tickets

Let me further broaden this discussion to include github branches, which are often linked on tickets, and then later deleted. This forces a person to search through git to actually see the patch, and that process can be a little rough (especially since we all know if you're gonna make a typo, it's

Re: Contribute to the Cassandra wiki

I've added you. On Sun, Mar 12, 2017 at 1:43 PM, ThisHosting.Rocks! < contact@thishosting.rocks> wrote: > Hi, > > > My username is NickReiner and I'd like to contribute to the Cassandra wiki. > > Please. :) > > Nick Reiner > THR Support. >

Re: [VOTE] Ask Infra to move github notification emails to commits@

+1, we've had to explain this a thousand times here. On Mon, Mar 20, 2017 at 5:00 PM, Jeff Jirsa wrote: > There's no reason for the dev list to get spammed everytime there's a > github PR. We know most of the time we prefer JIRAs for real code PRs, but > with docs being in tree and low barrier t

Re: [VOTE] Ask Infra to move github notification emails to commits@

I think this is a better solution. On Mon, Mar 20, 2017 at 5:03 PM, Blake Eggleston wrote: > Maybe we should add p...@cassandra.apache.org or something and send them > there? I don't subscribe to commits@ because it's too much email, I would > be interested in being notified when a PR is opened

Re: [VOTE] Ask Infra to move github notification emails to commits@

I retract my +1 and think instead we should open a vote on Blake's idea. On Mon, Mar 20, 2017 at 5:20 PM, Brandon Williams wrote: > I think this is a better solution. > > On Mon, Mar 20, 2017 at 5:03 PM, Blake Eggleston > wrote: > >> Maybe we should add p...@cassand

Re: [VOTE] Ask Infra to move github notification emails to pr@

+1 On Mon, Mar 20, 2017 at 5:32 PM, Jeff Jirsa wrote: > There's no reason for the dev list to get spammed everytime there's a > github PR. We know most of the time we prefer JIRAs for real code PRs, but > with docs being in tree and low barrier to entry, we may want to accept > docs through PRs

Re: Weekly Cassandra Wrap-up

Not specific to C*, but still sjk plus a million times over: https://github.com/aragozin/jvm-tools On Mon, Apr 3, 2017 at 4:17 PM, Jeff Jirsa wrote: > Monday follow-up: > > There exist a lot of tools that a lot of people know exist and use for > managing clusters. Examples are repair scripts li

Re: Weekly Cassandra Wrapup

No. On Mon, Apr 10, 2017 at 3:07 PM, Cindy Wang wrote: > unsubscribe > > On 10 April 2017 at 09:33, Eric Evans wrote: > > > On Fri, Apr 7, 2017 at 10:35 PM, Jeff Jirsa wrote: > > > First, check out this graph: > > > > > > http://i.imgur.com/cEx3jOo.png > > > > Oh snap; That's awesome! > > > >

Re: [VOTE] Release Apache Cassandra 3.0.13

+1 On Tue, Apr 11, 2017 at 1:59 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.13. > > sha1: 91661ec296c6d089e3238e1a72f3861c449326aa > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.13-tentative > Artifacts: > https:

Re: Definition of QUORUM consistency level

We have CL.TWO. On Thu, Jun 8, 2017 at 10:03 PM, Dikang Gu wrote: > So, for the quorum, what we really want is that there is one overlap among > the nodes in write path and read path. It actually was my assumption for a > long time that we need (N/2 + 1) for write and just need (N/2) for read, >

Re: Definition of QUORUM consistency level

I don't disagree with you there and have never liked TWO/THREE. This is somewhat relevant: https://issues.apache.org/jira/browse/CASSANDRA-2338 I don't think going to CL.FOUR, etc, is a good long-term solution, but I'm also not sure what is. On Thu, Jun 8, 2017 at 11:20 PM, Dikang Gu wrote: >

Re: [VOTE] Release Apache Cassandra 3.0.14

+1 On Mon, Jun 19, 2017 at 3:37 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.14. > > sha1: f3e38cb638113c2a23855a104d6082da5bc10ddb > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.0.14-tentative > Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 3.11.0

+1 On Mon, Jun 19, 2017 at 6:10 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.0. > > sha1: 88dee7e9d515ad94ecf8f2309f1e6138ec79e1a2 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.11.0-tentative > Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 2.2.10

+1 On Wed, Jun 21, 2017 at 3:20 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.10. > > sha1: 83f28ce3c4eeff75ce70855a56b6155047ce8e9a > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.2.10-tentative > Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 2.1.18

+1 On Wed, Jun 21, 2017 at 3:18 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.18. > > sha1: 9369db1dfd92d4eb76284cfb68b1ffb9d22c9b06 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.1.18-tentative > Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 2.1.19

+1 On Sep 28, 2017 1:12 PM, "Michael Shuler" wrote: > I propose the following artifacts for release as 2.1.19. > > sha1: 428eaa3e37cab7227c81fdf124d29dfc1db4257c > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.1.19-tentative > Artifacts: > https://repo

Re: [VOTE] Release Apache Cassandra 2.2.11

+1 On Sep 28, 2017 1:41 PM, "Michael Shuler" wrote: > I propose the following artifacts for release as 2.2.11. > > sha1: c510e001481637e1f74d9ad176f8dc3ab7ebd1e3 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.2.11-tentative > Artifacts: > https://repo

Re: [VOTE] Release Apache Cassandra 3.0.15

+1 On Oct 2, 2017 12:58 PM, "Aleksey Yeshchenko" wrote: > +1 > > — > AY > > On 2 October 2017 at 18:18:26, Michael Shuler (mich...@pbandjelly.org) > wrote: > > I propose the following artifacts for release as 3.0.15. > > sha1: b32a9e6452c78e6ad08e371314bf1ab7492d0773 > Git: > http://git-wip-us.a

Re: [VOTE] Release Apache Cassandra 3.11.1

+1 On Mon, Oct 2, 2017 at 12:58 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.1. > > sha1: 983c72a84ab6628e09a78ead9e20a0c323a005af > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.11.1-tentative > Artifacts: > https:

Re: URGENT: CASSANDRA-14092 causes Data Loss

My guess is they don't know how to NOT set a TTL (perhaps with a default in the schema), so they chose max value. Someone else's problem by then. On Thu, Jan 25, 2018 at 2:38 PM, Michael Kjellman wrote: > why are people inserting data with a 15+ year TTL? sorta curious about the > actual use ca

Re: [VOTE] Release Apache Cassandra 2.2.12

+1 On Mon, Feb 12, 2018 at 2:30 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.12. > > sha1: 1602e606348959aead18531cb8027afb15f276e7 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.2.12-tentative > Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 2.1.20

+1 On Mon, Feb 12, 2018 at 2:30 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.20. > > sha1: b2949439ec62077128103540e42570238520f4ee > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/2.1.20-tentative > Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 3.11.2

+1 On Mon, Feb 12, 2018 at 2:31 PM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.2. > > sha1: f6ec5c5d18c2900af0ef6e314edbd19aaa682a55 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= > shortlog;h=refs/tags/3.11.2-tentative > Artifacts: > https:

Re: [VOTE] Release Apache Cassandra 3.0.16

+1 On Mon, Feb 12, 2018 at 2:31 PM, Michael Shuler 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:

Re: [VOTE] Release Apache Cassandra 3.0.16

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 messa

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

I change my vote to -1 binding here, too. On Tue, Feb 13, 2018 at 3:45 PM, Jason Brown wrote: > -1, binding. Unit tests are broken: > https://circleci.com/gh/jasobrown/cassandra/452#tests/containers/60 > > > Dave ninja-committ

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

+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:

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

+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:

Re: Cassandra Needs to Grow Up by Version Five!

The only progress from this point is what Jon said: enumerate and detail your issues in jira tickets. On Wed, Feb 21, 2018 at 4:53 PM, Kenneth Brotman < kenbrot...@yahoo.com.invalid> wrote: > Hi Akash, > > I get the part about outside work which is why in replying to Jeff Jirsa I > was suggesting

Re: Debug logging enabled by default since 2.2

It seems to me the power user who wants to eek out that last bit of performance can do so. It also seems like the user who doesn't even know about that is the exact kind of user that's going to need the debug log in the future. On Sun, Mar 18, 2018 at 1:45 PM, Michael Kjellman wrote: > i’m not

Re: [VOTE] Release Apache Cassandra 5.0-rc1 (take3)

+1 Note that centos7 went EOL on June 30th; I didn't test the noboolean packages as a result. Kind Regards, Brandon On Wed, Jul 10, 2024 at 2:54 PM Mick Semb Wever wrote: > > Proposing the third test build of Cassandra 5.0-rc1 for release. > > sha1: d85d6750f90eaf799709a05d2f1c31189fce04fd > Gi

Re: [VOTE] Release Apache Cassandra 5.0-rc1 (take3)

On Wed, Jul 17, 2024 at 2:36 PM Mick Semb Wever wrote: > > Should we remove the noboolean rpm from the release, given we have no way to > verify or test it ? > Effectively, dropping centos:7 support from 5.0. I didn't look into whether or not there were other distros that might need it. I shoul

Re: Welcome Joey Lynch as Cassandra PMC member

Congrats! Kind Regards, Brandon On Wed, Jul 24, 2024 at 9:12 AM Benjamin Lerer wrote: > > The PMC's members are pleased to announce that Joey Lynch has accepted the > invitation to become a PMC member. > > Thanks a lot, Joey, for everything you have done for the project all these > years. > >

Re: [RESULT}[VOTE] Release Apache Cassandra 5.0-rc1

A release is always coming ;) I'll try to get the 4.1.6 ball rolling on Monday. Kind Regards, Brandon On Wed, Jul 24, 2024 at 3:56 PM Elliott Sims via dev wrote: > > Looks like this is out and there's a 5.0-rc release. Is a 4.1.6 release with > a fix for CASSANDRA-19668 coming? > > On Sat, Ju

Re: [DISCUSS] Backport CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0

Given how low risk this is, I don't see an issue with backporting it and I'm sure the usefulness outweighs what risk there is. +1 (5.0.1 though, not 5.0.0) Kind Regards, Brandon On Fri, Jul 26, 2024 at 11:52 AM Yifan Cai wrote: > > Hi everyone, > > CASSANDRA-19800 is currently in the state of re

[VOTE] Release Apache Cassandra 4.1.6

Proposing the test build of Cassandra 4.1.6 for release. sha1: b662744af59f3a3dfbfeb7314e29fecb93abfd80 Git: https://github.com/apache/cassandra/tree/4.1.6-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1339/org/apache/cassandra/cassandra-all/4.1.6

Re: [DISCUSS] introduction of SnapshotManagerMBean

On Thu, Aug 1, 2024 at 9:22 AM Jon Haddad wrote: > I don't think we've deprecated or removed anything that mentions "column > family" or "cf" even though that hasn't been our user-facing terminology in > close to a decade. Please correct me if I'm wrong on any of this. Off the top of my head

Re: [DISCUSS] state of lz4-java

I just want to note that lz4 is used for network compression, either between nodes or more importantly for clients, so interoperability is key and we need to be careful about changing things here. Kind Regards, Brandon On Fri, Aug 2, 2024 at 3:05 AM Štefan Miklošovič wrote: > > I just want to ra

Re: [VOTE] Release Apache Cassandra 4.1.6

existing API should be followed. > > Maybe we should have an exhaustive list of public APIs, and explicitly > mention that native and internode protocols are included, alongside with > nodetool command API and output, but also which classes/interfaces > specifically should

Re: [VOTE] Backport CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0

+1 for reasons stated in the discussion. Kind Regards, Brandon On Sun, Aug 4, 2024 at 1:18 AM Yifan Cai wrote: > > Hi, > > I am proposing backporting CASSANDRA-19800 to Cassandra-4.0, 4.1 and 5.0. > > There is a discussion thread on the topic. In summary, the backport would > benefit Cassandra

Re: [VOTE] Release Apache Cassandra 4.1.6

t; >> > Given we allow a pluggable query handler implementation to be specified >> > for the server with a -D during startup. So I would consider the query >> > handler one of our public interfaces. >> > >> > On Jul 30, 2024, at 9:35 AM, Alex Petrov wrote:

[VOTE] Release Apache Cassandra 4.1.6 - take 2

Proposing the test build of Cassandra 4.1.6 for release. sha1: 790de1079811278a2b431c2ced7c7ea02d290a25 Git: https://github.com/apache/cassandra/tree/4.1.6-tentative Maven Artifacts: https://repository.apache.org/content/repositories/orgapachecassandra-1340/org/apache/cassandra/cassandra-all/4.1.6

Re: [VOTE] Release Apache Cassandra 4.1.6 - take 2

+1 On Wed, Aug 14, 2024 at 11:54 AM Brandon Williams wrote: > > Proposing the test build of Cassandra 4.1.6 for release. > > sha1: 790de1079811278a2b431c2ced7c7ea02d290a25 > Git: https://github.com/apache/cassandra/tree/4.1.6-tentative > Maven Artifacts: > https://reposito

Re: [VOTE] Release Apache Cassandra 4.1.6 - take 2

With five +1 (four binding) and no -1, the vote passes. I'll work on getting the release published. On Wed, Aug 14, 2024 at 11:54 AM Brandon Williams wrote: > > Proposing the test build of Cassandra 4.1.6 for release. > > sha1: 790de1079811278a2b431c2ced7c7ea02d290a25 > Git

[RELEASE] Apache Cassandra 4.1.6 released

[RELEASE] Apache Cassandra 4.1.6 released The Cassandra team is pleased to announce the release of Apache Cassandra version 4.1.6. Apache Cassandra is a fully distributed database. It is the right choice when you need scalability and high availability without compromising performance. http://ca

Re: [VOTE] Release Apache Cassandra 5.0-rc2

+1 Kind Regards, Brandon On Thu, Aug 22, 2024 at 6:58 AM Mick Semb Wever wrote: > > > Proposing the test build of Cassandra 5.0-rc2 for release. > > sha1: 06691fce25a215361332aa1767e188bb6694687a > Git: https://github.com/apache/cassandra/tree/5.0-rc2-tentative > Maven Artifacts: > https://repo

Re: Welcome Jordan West and Stefan Miklosovic as Cassandra PMC members!

Congrats to you both! Kind Regards, Brandon On Fri, Aug 30, 2024 at 3:21 PM Jon Haddad wrote: > > The PMC's members are pleased to announce that Jordan West and Stefan > Miklosovic have accepted invitations to become PMC members. > > Thanks a lot, Jordan and Stefan, for everything you have done

Re: [VOTE] Release Apache Cassandra 5.0.0

I agree neither seems to be a blocker as long as 1) is still clean, +1. Kind Regards, Brandon On Wed, Sep 4, 2024 at 7:47 AM Štefan Miklošovič wrote: > > I am +1 but I found two "issues" along the way. > > for 1) I do not think this is a blocker, what is important is that at the > time of the r

Re: [VOTE] Release test-api 0.0.17

+1 Kind Regards, Brandon On Tue, Sep 10, 2024 at 9:36 AM Doug Rohrer wrote: > > Proposing the test build of in-jvm dtest API 0.0.17 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-d

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

On Thu, Sep 12, 2024 at 11:07 AM Caleb Rackliffe wrote: > > The one consequence of that we might discuss here is that if gossip is behind > in notifying a node with a pending range, local rejection as it receives > writes for that range may cause a small issue of availability. I don't think thi

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

On Thu, Sep 12, 2024 at 11:41 AM Caleb Rackliffe wrote: > > Are you opposed to the patch in its entirety, or just rejecting unsafe > operations by default? I had the latter in mind. Changing any default in a patch release is a potential surprise for operators and one of this nature especially s

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

On Thu, Sep 12, 2024 at 11:52 AM Josh McKenzie wrote: > > More or less surprising than learning that they've been at risk of or > actively losing data for years? Ignorance is bliss though and I think the majority of users haven't lost sleep over this since it's been present since the beginning o

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

On Thu, Sep 12, 2024 at 1:13 PM Caleb Rackliffe wrote: > > I think I can count at least 4 people on this thread who literally have lost > sleep over this. Probably good examples of not being the majority though, heh. If we are counting on users to read NEWS.txt, can we not count on them to enab

Re: Welcome Chris Bannister, James Hartig, Jackson Flemming and João Reis, as cassandra-gocql-driver committers

Congratulations! Kind Regards, Brandon On Thu, Sep 12, 2024 at 6:40 AM Mick Semb Wever wrote: > > The PMC's members are pleased to announce that Chris Bannister, James Hartig, > Jackson Flemming and João Reis have accepted invitations to become committers > on the Drivers subproject. > > Thank

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

On Thu, Sep 12, 2024 at 8:34 PM Josh McKenzie wrote: > I'm not advocating for us having a rigid principled stance where we reject > all nuance and don't discuss things. I'm advocating for us coalescing on a > shared default stance of correctness unless otherwise excepted. We know we're > a dive

Re: [DISCUSS] CASSANDRA-13704 Safer handling of out of range tokens

+1 for declaring things like this in the vote/release emails. Kind Regards, Brandon On Sun, Sep 15, 2024 at 10:17 AM Michael Shuler wrote: > > I've stated this same opinion prior, fix was in NEWS.txt and users had a > bad day with a behavior change. Perhaps this kind of inclusion needs > more ex

Re: [DISCUSS] Chronicle Queue's development model and a hypothetical replacement of the library

My concern is that we have to keep making sure it's not phoning home(1,2). (1) https://issues.apache.org/jira/browse/CASSANDRA-18538 (2) https://issues.apache.org/jira/browse/CASSANDRA-19656 Kind Regards, Brandon On Mon, Sep 16, 2024 at 7:53 PM Josh McKenzie wrote: > > I think it's FQLTool only

Re: [VOTE] Release Apache Cassandra 1.1.2

+1 On Jun 29, 2012 11:21 AM, "Sylvain Lebresne" wrote: > We've fixed a fair amount of issues so I believe it is time for a new > release > and thus propose the following artifacts for release as 1.1.2. > > sha1: b94d8d40fb6f84b4041857bf69ddf7cd22df2e86 > Git: > http://git-wip-us.apache.org/repos/

Re: [VOTE] Release Apache Cassandra 1.0.11

+1 On Fri, Jul 27, 2012 at 11:38 AM, Sylvain Lebresne wrote: > The 1.0 branch is fairly stable now but we still have fixed a few bugs since > 1.0.10 so I propose the following artifacts for release as 1.0.11. > > sha1: 4f0237acd5ee8097f90732ac416622588e4d7552 > Git: > http://git-wip-us.apache.or

Re: findbugs

On Mon, Jul 30, 2012 at 9:52 AM, Jonathan Ellis wrote: > Is Jenkins smart enough to be able to say, "I know we had X findbugs > warnings previously, which are known to be false positives, but now > there are X+1" ? In my experience, jenkins hasn't even been smart enough to build cassandra in a co

Re: [VOTE] Release Apache Cassandra 1.1.3

On Tue, Jul 31, 2012 at 5:23 AM, Sylvain Lebresne wrote: > Some fair amount of bug have been fixed since 1.1.2, including a few important > ones, so I propose the following artifacts for release as 1.1.3. It looks like we need to get https://issues.apache.org/jira/browse/CASSANDRA-4427 sorted aga

Re: [VOTE] Release Apache Cassandra 1.1.3 (Strike 2)

Oops, can we also add the small fix from https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commitdiff;h=6dfb3a8557a39ac22dccbf3c597f558d310fb7e8 ? On Wed, Aug 1, 2012 at 1:29 PM, Sylvain Lebresne wrote: > Let's try that again. I propose the following artifacts for release as 1.1.3. > > sh

Re: [VOTE] Release Apache Cassandra 1.1.3 (Strike 3)

+1 On Thu, Aug 2, 2012 at 1:43 AM, Sylvain Lebresne wrote: > Hopefully for the last time I propose the following artifacts for > release as 1.1.3. > > sha1: 94bcc6a6f6171796e3147dec73d71df05c370f94 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/1.1.3-tenta

<    1   2   3   4   5   6   7   8   9   10   >