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

2016-10-10 Thread Brandon Williams
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

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

2016-10-10 Thread Michael Shuler
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 tagged with fixver of '2.1.x' in JIRA? Is this minor improvement satisfactory for a the critical-only nature of the 2.1 branch and go into the next 2.1

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-10 Thread Nate McCall
> It's too minor for a re-roll, and safe enough to just apply yourself if you > want it. Agreed. > > 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 Romai

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-10 Thread Brandon Williams
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: [VOTE] Release Apache Cassandra 2.1.16

2016-10-10 Thread Michael Shuler
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 speaking up about this, but I stuck with my +1 in > order to get 2.1.16 with the NTR fix out since I have seen > CASSANDRA-11363 with every recent client insta

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-10 Thread Nate McCall
Hi Romain, I appreciate you speaking up about this, but I stuck with my +1 in order to get 2.1.16 with the NTR fix out since I have seen CASSANDRA-11363 with every recent client installation. Also, running the patch in production produced results satisfactory enough to me to preclude the need for e

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-07 Thread Jason Brown
Ahh, sorry. I was +1'ing the proposed sha1 of 87034cd On Friday, October 7, 2016, Michael Shuler wrote: > On 10/07/2016 08:52 AM, Jason Brown wrote: > > +1 > > Jason, is this a vote for the proposed sha1: 87034cd release for 2.1.16, > or a comment to Romain? (gmail lacks some In-Reply-To/Refere

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-07 Thread Michael Shuler
On 10/07/2016 08:52 AM, Jason Brown wrote: > +1 Jason, is this a vote for the proposed sha1: 87034cd release for 2.1.16, or a comment to Romain? (gmail lacks some In-Reply-To/References intelligence sometimes, so just clarifying) > On Thu, Oct 6, 2016 at 3:45 PM, Romain Hardouin > wrote: > >> I'

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-07 Thread Jason Brown
+1 On Thu, Oct 6, 2016 at 3:45 PM, Romain Hardouin wrote: > Hi, > I use the "current 2.1.16" (commit cdd535fcac4ba79bb371e8373c6504d9e3978853) > on > production in 5 DCs (82 nodes) out of 7 and it works well!I've just had to > add a MBean to track changes of the NTR queue length on top of cdd53

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-06 Thread Romain Hardouin
Hi, I use the "current 2.1.16" (commit cdd535fcac4ba79bb371e8373c6504d9e3978853) on production in 5 DCs (82 nodes) out of 7 and it works well!I've just had to add a MBean to track changes of the NTR queue length on top of cdd535f. This allow to make correlations with other metrics and see the im

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-06 Thread Tyler Hobbs
+1 On Wed, Oct 5, 2016 at 6:09 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:/

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-06 Thread Aleksey Yeschenko
+1 --  AY On 6 October 2016 at 15:32:46, Gary Dusbabek (gdusba...@gmail.com) wrote: +1 On Wed, Oct 5, 2016 at 6:09 PM, Michael Shuler wrote: > I propose the following artifacts for release as 2.1.16. > > sha1: 87034cd05964e64c6c925597279865a40a8c152f > Git: > http://git-wip-us.a

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-06 Thread Gary Dusbabek
+1 On Wed, Oct 5, 2016 at 6:09 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:/

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-05 Thread Jeff Jirsa
+1 On 2016-10-05 16:09 (-0700), 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://re

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-05 Thread Nate McCall
+1 On Thu, Oct 6, 2016 at 12:09 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://re

Re: [VOTE] Release Apache Cassandra 2.1.16

2016-10-05 Thread Brandon Williams
+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