Re: ACNA 2019 Schedule is out

2019-06-09 Thread Nate McCall
The topics look really interesting. Do you know if it will be recorded for > people to catch up later? > > Regards > > That's being discussed on the conference planning list. Unfortunately at this point It doesnt look like they have the budget/volunteers for it this year.

Re: ACNA 2019 Schedule is out

2019-06-07 Thread Nate McCall
te On Fri, Jun 7, 2019 at 11:18 AM Nate McCall wrote: > Hi Folks, > Thanks to everyone who submitted talks and helped out reviewing. We ended > up with a lot more material than we could make room for, but I think we put > together what will be a good track: > https://www.apachecon.

ACNA 2019 Schedule is out

2019-06-06 Thread Nate McCall
Hi Folks, Thanks to everyone who submitted talks and helped out reviewing. We ended up with a lot more material than we could make room for, but I think we put together what will be a good track: https://www.apachecon.com/acna19/schedule.html If you submitted a talk and got accepted the ASF folks

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-28 Thread Nate McCall
ensive testing. Maybe its really time to > hit> > > > it!> > > > > > :-)> > > > > > >>> > > > > > >> Attila Wind> > > > > > >>> > > > > > >> htt

[DISCUSS] Moving chats to ASF's Slack instance

2019-05-28 Thread Nate McCall
Hi Folks, While working on ApacheCon last week, I had to get setup on ASF's slack workspace. After poking around a bit, on a whim I created #cassandra and #cassandra-dev. I then invited a couple of people to come signup and test it out - primarily to make sure that the process was seamless for

Re: "4.0: TBD" -> "4.0: Est. Q4 2019"?

2019-05-27 Thread Nate McCall
tflix.com.INVALID> wrote: > > >>>> > > >>>> Having at least a ballpark target on the website will definitely > help. > > >> +1 > > >>>> on setting it to Q4 2019 for now. > > >>>> > > >>>> On Thu, May 23, 2019

Re: Review ApacheCon Cassandra track submissions

2019-05-25 Thread Nate McCall
Thanks for everyone to volunteered. I'll be sending out instructions later today. Cheers, -Nate On Mon, May 20, 2019 at 9:07 PM Nate McCall wrote: > Hi Folks, > As you probably know, the ApacheCon NA CFP recently closed. We received *a > lot* of submissions for the Cassandra trac

Re: Review ApacheCon Cassandra track submissions

2019-05-21 Thread Nate McCall
have entire PMC vote on talks? > > 2) We need to do t-shirts. :) Do we need corporate sponsorship for that > > (i.e. $$)? I can look into that if so. > > > > On Tue, May 21, 2019 at 12:28 AM Nate McCall wrote: > > > >> Hi Folks, > >> As you

Review ApacheCon Cassandra track submissions

2019-05-20 Thread Nate McCall
Hi Folks, As you probably know, the ApacheCon NA CFP recently closed. We received *a lot* of submissions for the Cassandra track (thanks everyone!!!). 3x more than any other project specific track and *almost* as much as the catch-all big data track. Not only that, but there are a lot of good

Re: Two day Apache Cassandra track at ApacheConNA 2019

2019-05-07 Thread Nate McCall
*Bump* Just a reminder we are still accepting submissions for NGCC and our user track at ApacheCon: https://www.apachecon.com/acna19/cfp.html Thanks to the folks who have submitted so far!! Cheers, -Nate On Wed, Mar 13, 2019 at 1:22 PM Nate McCall wrote: > Hi Folks, > > I am

GSoD update: new mail list for inbounds

2019-05-05 Thread Nate McCall
Hi Folks, For those that have offered to help GSoD efforts, please subscribe to the following list publicly accessible, but moderated list: gsod2...@cassandra.apache.org Ie. as with any ASF list, send an email to gsod2019-subscr...@cassandra.apache.org with SUBSCRIBE as the subject, reply to the

Re: GSoD Exploration Information

2019-05-01 Thread Nate McCall
Hi Himanshu, Thanks for reaching out regarding the GSoD project. However, GSoD itself has the requirement of previous technical writing experience. I'm not sure you are able to participate through the program without such? That being said, as an open source project, we are certainly willing to

Apache Cassandra Accepted to GSoD

2019-04-30 Thread Nate McCall
Hi Folks, Quick update to say that we got accepted to Google's Season of Docs project: https://developers.google.com/season-of-docs/docs/participants/ Outline of potential projects is here for reference: https://cwiki.apache.org/confluence/display/CASSANDRA/Apache+Cassandra+GSoD+2019+application

Re: TLP tools for stress testing and building test clusters in AWS

2019-04-16 Thread Nate McCall
Just noticed the date - to be clear, this is like in ~45 mins? On Wed, Apr 17, 2019 at 12:11 PM Nate McCall wrote: > > > I have set up a zoom link for the TLP tool set intro that will be on in an > > hours time (17 April 2019 @ 11:00AM AEST): https://zoom.us/j/272648772 > >

Re: TLP tools for stress testing and building test clusters in AWS

2019-04-16 Thread Nate McCall
> I have set up a zoom link for the TLP tool set intro that will be on in an > hours time (17 April 2019 @ 11:00AM AEST): https://zoom.us/j/272648772 > Super rad - thanks for setting this up, Anthony! - To unsubscribe, e-mail:

Re: Stabilising Internode Messaging in 4.0

2019-04-14 Thread Nate McCall
trary LoC or complexity metric, that's fine, but > let's not retcon this and try and impose restrictions or interpretations on > peoples' behavior after the fact. > > Everyone acted in good faith here. Collaborating internationally with > dozens of engineers is Hard; let's assume the

Re: Stabilising Internode Messaging in 4.0

2019-04-12 Thread Nate McCall
As someone who has been here a (very) long time and worked on C* in production envs. back to version 0.4, this large patch - taken by itself - does, to be frank, scare the shit out of me. In a complex system any large change will have side effects impossible to anticipate. I have seen this hold

Re: need information

2019-03-31 Thread Nate McCall
Hi Amit, The ASF product name usage guidelines would be a good place to start: http://www.apache.org/foundation/marks/guide Give that a read and let us know if you have any questions. Thanks reaching out about this either way. Cheers, -Nate On Sat, Mar 30, 2019 at 10:54 AM Dinesh Joshi wrote:

Two day Apache Cassandra track at ApacheConNA 2019

2019-03-12 Thread Nate McCall
Hi Folks, I am delighted to share with you that we, the Apache Cassandra community, have been given a two day track at this year's ApacheCon North America. The goal of this track is simple: we are going to get together to talk about Apache Cassandra. As such, this will be the ideal place to

Re: [VOTE] Release Apache Cassandra 3.0.18

2019-02-03 Thread Nate McCall
On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler wrote: > > I propose the following artifacts for release as 3.0.18. > > sha1: edd52cef50a6242609a20d0d84c8eb74c580035e > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.18-tentative > Artifacts: >

Re: [VOTE] Release Apache Cassandra 2.2.14

2019-02-03 Thread Nate McCall
On Sat, Feb 2, 2019 at 4:32 PM Michael Shuler wrote: > > I propose the following artifacts for release as 2.2.14. > > sha1: af91658353ba601fc8cd08627e8d36bac62e936a > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.14-tentative > Artifacts: >

Re: [VOTE] Release Apache Cassandra 3.11.4

2019-02-03 Thread Nate McCall
On Sat, Feb 2, 2019 at 4:38 PM Michael Shuler wrote: > > I propose the following artifacts for release as 3.11.4. > > sha1: fd47391aae13bcf4ee995abcde1b0e180372d193 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.4-tentative > Artifacts: >

Re: [VOTE] Release Apache Cassandra 2.1.21

2019-02-03 Thread Nate McCall
+1 on the release of 2.1.21 (let's focus on that in the spirit of these other votes we have up right now). I don't feel the need to be absolutist about something being EOL. On Sun, Feb 3, 2019 at 1:47 AM Stefan Podkowinski wrote: > > What are we voting on here? Releasing the 2.1.21 candidate,

Re: Cassandra website docs for 3.11 added

2019-01-07 Thread Nate McCall
This is fantastic!! Thanks a bunch for the effort on this, folks. On Mon, Jan 7, 2019 at 4:31 PM Mick Semb Wever wrote: > > > > Next step it to regenerate the docs for Cassandra-4.0 (latest). I'll do > > this next week if no one objects. > > > This has been done by Joey Lynch, Anthony Grasso and

Re: [VOTE] Change Jira Workflow

2018-12-17 Thread Nate McCall
On Tue, Dec 18, 2018 at 4:19 AM Benedict Elliott Smith wrote: > > I propose these changes > * > to the Jira Workflow for the project. The vote will be open for 72 hours**. > +1

Re: JIRA Workflow Proposals

2018-12-05 Thread Nate McCall
> Summary: > > 1: Component. (A) Multi-select; (B) Cascading-select > 2: Labels: leave alone +1/-1 > 3: No workflow changes for first/second review: +1/-1 > 4: Priorities: Including High +1/-1 > 5: Mandatory Platform and Feature: +1/-1 > 6: Remove Environment field: +1/-1 > 1: A 2: +1 3: +1 4: +1

Re: 4.0 Testing Signup

2018-11-08 Thread Nate McCall
Thanks Romain! Let's keep a top level ticket for the/a component, but add child tasks as needed. I think child tickets are a little easier to manage than using a tag or similar. On Thu, Nov 8, 2018 at 11:04 AM Romain Hardouin wrote: > > > Hi, > I'm volunteer to be contributor on Metrics or

Re: Jepsen testing

2018-11-08 Thread Nate McCall
[- cassandra-users] Hi Yuji, Thanks so much for working on this! Any fault injection testing is certainly worth the effort. Thanks, -Nate On Thu, Nov 8, 2018 at 1:36 PM Yuji Ito wrote: > > Hi, > > We are working on Jepsen testing for Cassandra. >

Re: Testing 4.0 upgrading

2018-10-24 Thread Nate McCall
> Now I will reinstall the old version and do the upgrade again and > hopefully I can have more information soon. > Hi Tommy, Thanks for taking the time to brave an upgrade test this early on - it is super helpful to get this feedback. Anyone else that has bandwidth, we very much appreciate

Re: TSU NOTIFICATION - Encryption

2018-09-24 Thread Nate McCall
Just some housekeeping paper work for export controls per: http://www.apache.org/licenses/exports/ See https://issues.apache.org/jira/browse/CASSANDRA-14634 and https://issues.apache.org/jira/browse/LEGAL-358 if you're curios. On Tue, Sep 25, 2018 at 5:28 PM Nate McCall wrote: > > SUBM

TSU NOTIFICATION - Encryption

2018-09-24 Thread Nate McCall
SUBMISSION TYPE: TSU SUBMITTED BY: Nate McCall SUBMITTED FOR:The Apache Software Foundation POINT OF CONTACT: Secretary, The Apache Software Foundation FAX: +1-919-573-9199 MANUFACTURER(S): The Apache Software Foundation, Oracle, The OpenSSL

Re: [DISCUSS] changing default token behavior for 4.0

2018-09-23 Thread Nate McCall
Let's pick a default setup that works for most people (IME clusters < 30 nodes, but TLP and Instaclustr peeps probably have the most insight here). Then we just explain the heck out of it in the comments. I would also like to see this include some details add/remove a DC to change the values

[RESULT] [VOTE] Accept GoCQL driver donation and begin incubation process

2018-09-20 Thread Nate McCall
With four binding +1s, 2 +0s, and no -1s, and 6 non-binding +1s, the vote passes. To re-iterate, resolving the license concerns is part of bringing software into the project, not a reason to avoid trying. The incubator PMC will have no problem sending a -1 if we cant get everything together.

[VOTE] Accept GoCQL driver donation and begin incubation process

2018-09-12 Thread Nate McCall
This will be the same process used for dtest. We will need to walk this through the incubator per the process outlined here: https://incubator.apache.org/guides/ip_clearance.html Pending the outcome of this vote, we will create the JIRA issues for tracking and after we go through the process,

Re: [Discuss] Accept GoCQL driver donation

2018-09-12 Thread Nate McCall
ecoming an officially endorsed golang > > Cassandra driver. Makes a lot of sense too. > > > > Alex. > > > > > > On Sat., 1 Sep. 2018, 01:08 Chris Bannister, > > wrote: > > > > > I intend to stay on and continue to contribute. > > > >

[Discuss] Accept GoCQL driver donation

2018-08-31 Thread Nate McCall
Hi folks, So I was recently talking with, Chris Bannister the gocql [0] maintainer, and he expressed an interest in donating the driver to the ASF. We could accept this along the same lines as how we took in the dtest donation - going through the incubator IP clearance process [1], but in this

Re: Proposing an Apache Cassandra Management process

2018-08-17 Thread Nate McCall
> I'm not sure logistically how we get a new repo created and licensing and > such, but if someone helps make it we can cut the patch against it > This is pretty straight forward. For precedent, see: https://issues.apache.org/jira/browse/CASSANDRA-13634 We currently have three repositories:

Re: Apache Cassandra Blog is now live

2018-08-07 Thread Nate McCall
It's just another contribution so JIRA + patch should suffice. On Wed, Aug 8, 2018 at 2:11 PM, Dikang Gu wrote: > The fast streaming is very cool! > > We are also interested in contributing to the blog, what's the process? > > Thanks > Dikang. > > On Tue, Aug 7, 201

Re: Apache Cassandra Blog is now live

2018-08-07 Thread Nate McCall
You can tell how psyched we are about it because we cross posted! Seriously though - this is by the community for the community, so any ideas - please send them along. On Wed, Aug 8, 2018 at 1:53 PM, sankalp kohli wrote: > Hi, > Apache Cassandra Blog is now live. Check out the first blog

Re: GitHub PR ticket spam

2018-08-05 Thread Nate McCall
I'd be fine with putting this traffic through as 'worklog' - good call, Mick! On Sun, Aug 5, 2018 at 7:56 PM, Mick Semb Wever wrote: >> I find this a bit annoying while subscribed to commits@, >> especially since we created pr@ for these kind of messages. Also I don't >> really see any value in

Re: Tracking Testing, Release Status, and Build Health

2018-07-29 Thread Nate McCall
Thanks for putting this together Scott! I like the idea of using Confluence for coordinating the bits and pieces on the way to 4.0. There are better things out there, but It's lightweight, straight forward and everyone with a ASF Jira account can participate. The one thing it does very well IMO

Re: [VOTE] Release Apache Cassandra 2.2.13

2018-07-25 Thread Nate McCall
+1 On Wed, Jul 25, 2018, 7:49 PM Michael Shuler wrote: > I propose the following artifacts for release as 2.2.13. > > sha1: 3482370df5672c9337a16a8a52baba53b70a4fe8 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.13-tentative > Artifacts: > >

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

2018-07-25 Thread Nate McCall
+1 On Wed, Jul 25, 2018, 7:47 PM Michael Shuler wrote: > I propose the following artifacts for release as 3.0.17. > > sha1: d52c7b8c595cc0d06fc3607bf16e3f595f016bb6 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.17-tentative > Artifacts: > >

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

2018-07-25 Thread Nate McCall
+1 On Wed, Jul 25, 2018, 7:46 PM Michael Shuler wrote: > I propose the following artifacts for release as 3.11.3. > > sha1: 31d5d870f9f5b56391db46ba6cdf9e0882d8a5c0 > Git: > > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.3-tentative > Artifacts: > >

Re: NGCC 2018?

2018-07-24 Thread Nate McCall
This was discussed amongst the PMC recently. We did not come to a conclusion and there were not terribly strong feelings either way. I don't feel like we need to hustle to get "NGCC" in place, particularly given our decided focus on 4.0. However, that should not stop us from doing an additional

Re: [VOTE] Branching Change for 4.0 Freeze

2018-07-13 Thread Nate McCall
+1 I appreciate Gary's points, but if it's not working and/or we have a specific issue, we'll address it. On Thu, Jul 12, 2018 at 9:46 AM, sankalp kohli wrote: > Hi, > As discussed in the thread[1], we are proposing that we will not branch > on 1st September but will only allow following

Re: [VOTE] Release Apache Cassandra 3.11.3

2018-07-02 Thread Nate McCall
+1 On Tue, Jul 3, 2018 at 8:11 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.11.3. > > sha1: aed1b5fdf1e953d19bdd021ba603618772208cdd > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.11.3-tentative > Artifacts: >

Re: [VOTE] Release Apache Cassandra 3.0.17

2018-07-02 Thread Nate McCall
+1 On Tue, Jul 3, 2018 at 8:10 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.17. > > sha1: c4e6cd2a1aca84a88983192368bbcd4c8887c8b2 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.17-tentative > Artifacts: >

Re: [VOTE] Release Apache Cassandra 2.2.13

2018-07-02 Thread Nate McCall
+1 On Tue, Jul 3, 2018 at 8:10 AM, Michael Shuler wrote: > I propose the following artifacts for release as 2.2.13. > > sha1: 9ff78249a0a5e87bd04bf9804ef1a3b29b5e1645 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/2.2.13-tentative > Artifacts: >

Re: Recommendation: running Cassandra in containers

2018-06-27 Thread Nate McCall
On Tue, Jun 26, 2018 at 3:12 AM, Pierre Mavro wrote: > Hi, > > Regarding the limits in linux cgroups (as used in Kubernetes/Mesos), I > was wondering if there are any recommendation (didn't find anything on > this topic). > > In general on Java 8 running instances, it is advised to run those >

Re: Hi-Rez of Apache Cassandra logo??

2018-06-26 Thread Nate McCall
Quick followup - here is a color pallet I pulled out of the logo: https://coolors.co/export/png/7b8f9a-3d3b3b-9d9c9c-65adcc-dbeaf2 Folks should feel free to use this for any C* related presentations. - To unsubscribe, e-mail:

CVE-2018-8016 on Apache Cassandra

2018-06-25 Thread Nate McCall
CVE-2018-8016 describes an issue with the default configuration of Apache Cassandra releases 3.8 through 3.11.1 which binds an unauthenticated JMX/RMI interface to all network interfaces allowing attackers to execute arbitrary Java code via an RMI request. This issue is a regression of the

Re: Rocksandra performance test result

2018-06-02 Thread Nate McCall
On Sat, Jun 2, 2018 at 4:46 PM, Jay Zhuang wrote: > We're shadowing some production traffics to a Rocksandra cluster ( > https://github.com/Instagram/cassandra/tree/rocks_3.0), the P99 latency is > significantly improved (about 6x for read, 12x for write). Here are the > test details: > >

Re: Rocksandra performance test result

2018-06-02 Thread Nate McCall
> Thanks for sharing, Jay. > > Could you say a bit more about how you’ve approached shadowing traffic > against an alternate cluster? (Asking not so much with regard to the > Rocksandra test, but toward shadowing methodology in general). +1 to this. If someone out there had a method to

Re: Hi-Rez of Apache Cassandra logo??

2018-05-18 Thread Nate McCall
ld be scalable to any > size you need. > > > > The above URLs are not permanent; since the list allows max-1MB > attachments, I've uploaded them to a temporary location. > > > > Happy to make changes or to share in another format if that works better. > >

Hi-Rez of Apache Cassandra logo??

2018-05-17 Thread Nate McCall
I'm looking for a hi-rez source of 'the eye' with "Apache Cassandra" (that last part is important) basically what we have on the website. I'm gonna run off some laptop stickers on sticker mule. Provided I can track that down, you can have one if you show up here:

Re: Roadmap for 4.0

2018-05-08 Thread Nate McCall
To close the loop on this thread: I don't think we need to do an official vote here, but let's just put it on our calendars that we are aiming to branch off 4.0 and freeze the first week of Sept. - To unsubscribe, e-mail:

Re: Evolving the client protocol

2018-04-23 Thread Nate McCall
Folks, Before this goes much further, let's take a step back for a second. I am hearing the following: Folks are fine with CASSANDRA-14311 and CASSANDRA-2848 *BUT* they don't make much sense from the project's perspective without a reference implementation. I think the shard concept is too

Re: Roadmap for 4.0

2018-04-12 Thread Nate McCall
> If we push it to Sept 1 freeze, I'll personally spend a lot of time testing. > > What can I do to help convince the Jun1 folks that Sept1 is acceptable? I can come around to that. At this point, I really just want us to have a date we can start talking to/planning around.

Re: Roadmap for 4.0

2018-04-12 Thread Nate McCall
To be clear, more who is willing to commit to testing should we go this route. On Fri, Apr 13, 2018, 7:41 AM Nate McCall <zznat...@gmail.com> wrote: > Ok. So who's willing to test 4.0 on June 2nd? Let's start a sign up. > > We (tlp) will put some resources on this via going thro

Re: Roadmap for 4.0

2018-04-12 Thread Nate McCall
Ok. So who's willing to test 4.0 on June 2nd? Let's start a sign up. We (tlp) will put some resources on this via going through some canned scenarios we have internally. We aren't in a position to test data validity (yet) but we can do a lot around cluster behavior. Who else has specific stuff

Re: Roadmap for 4.0

2018-04-10 Thread Nate McCall
A lot of good points and everyone's input is really appreciated. So it sounds like we are building consensus towards June 1 for 4.0 branch point/feature freeze and the goal is stability. (No one has come with a hard NO anyway). I want to reiterate Sylvain's point that we can do whatever we want

Re: Failed request after changing compression strategy from LZ4 to Deflate and using upgradesstable

2018-04-10 Thread Nate McCall
Hi Hitesh, This list is for conversations regarding Cassandra development. Can you subscribe and post this to us...@cassandra.apache.org instead? You will get a much wider audience when you do. On Tue, Apr 10, 2018 at 10:45 PM, hitesh dua wrote: > Hi, > My Compression

Re: Roadmap for 4.0

2018-04-09 Thread Nate McCall
> I'd like to see pluggable storage and transient replica tickets land, for > starters. I think both those features are, frankly, necessary for our future. On the other hand, they both have the following risks: 1. core behavioral changes 2. require changing a (relatively) large surface area of

Re: [Discuss] patch review virtual hackathon

2018-04-05 Thread Nate McCall
, it is hard to synchronize all people across > companies during one 72 hour slot. > > > > On Thu, Apr 5, 2018 at 9:48 PM, Nate McCall <zznat...@gmail.com> wrote: > > > Per Kurt's point in our release thread, we have a lot to do here. > > > > What do folks fee

[Discuss] patch review virtual hackathon

2018-04-05 Thread Nate McCall
Per Kurt's point in our release thread, we have a lot to do here. What do folks feel about setting aside a 72hr period at some point soon where we get some allotment from our employers to spend a window or two of time therein reviewing patches? I have seen a couple of other ASF communities do

Re: Roadmap for 4.0

2018-04-05 Thread Nate McCall
>> >> So long as non-user-visible improvements, including big ones, can still go >> in 4.0 at that stage, I’m all for it. > > > My understanding is that after June 1st the 4.0 branch would be created and > would be bugfix only. It's not really a feature freeze if you allow > improvements after

Re: Repair scheduling tools

2018-04-05 Thread Nate McCall
I think a take away here is that we can't assume a level of operation maturity will coincide automatically with scale. To make our core features robust, we have to account for less-experienced users. A lot of folks on this thread have *really* strong ops and OpsViz stories. Let's not forget that

Re: Repair scheduling tools

2018-04-05 Thread Nate McCall
> > Somewhat beside the point, I wasn't aware there were any 100 node + > clusters running with vnodes, if my math is correct they would be > excessively vulnerable to outages with that many vnodes and that many > nodes. Most of the large clusters I've heard of (100 nodes plus) are > running with

Re: Roadmap for 4.0

2018-04-05 Thread Nate McCall
>>> My understanding, from Nate's summary, was June 1 is the freeze date for >>> features. I expect we would go for at least 4 months (if not longer) >>> testing, fixing bugs, early dogfooding, and so on. I also equated June 1 >>> with the data which we would create a 'cassandra-4.0' branch, and

Re: Roadmap for 4.0

2018-04-04 Thread Nate McCall
Top-posting as I think this summary is on point - thanks, Scott! (And great to have you back, btw). It feels to me like we are coalescing on two points: 1. June 1 as a freeze for alpha 2. "Stable" is the new "Exciting" (and the testing and dogfooding implied by such before a GA) How do folks

Re: Roadmap for 4.0

2018-04-04 Thread Nate McCall
On Thu, Apr 5, 2018 at 3:26 AM, Kenneth Brotman wrote: > Can I suggest a way of defining the next few progressions as a way of > approaching this? > > How about something like this: > Version 4.0: A major release of as many improvements to the code as >

Re: Roadmap for 4.0

2018-04-03 Thread Nate McCall
> My concrete proposal would be to declare a feature freeze for 4.0 in 2 > months, > so say June 1th. That leave some time for finishing features that are in > progress, but not too much to get derailed. And let's be strict on that > freeze. I quite like this suggestion. Thanks, Sylvain. > After

Re: Repair scheduling tools

2018-04-03 Thread Nate McCall
This document does a really good job of listing out some of the issues of coordinating scheduling repair. Regardless of which camp you fall into, it is certainly worth a read. On Wed, Apr 4, 2018 at 8:10 AM, Joseph Lynch wrote: > I just want to say I think it would be

Re: A JIRA proposing a seperate repository for the online documentation

2018-03-18 Thread Nate McCall
On Mon, Mar 19, 2018 at 12:41 AM, Kenneth Brotman wrote: > I don't know what we are doing for the website technologies right now because > like everything else what we do is not documented anywhere. Where are the > servers: the cloud? What server software are we

Re: Expensive metrics?

2018-02-27 Thread Nate McCall
Hi Micke, There is some good research in here - have you had a chance to create some issues in Jira from this? On Fri, Feb 23, 2018 at 6:28 AM, Michael Burman wrote: > Hi, > > I was referring to this article by Shipilev (there are few small issues > forgotten in that url you

Re: Why isn't there a separate JVM per table?

2018-02-22 Thread Nate McCall
>>> performance profiling and cut down on the allocations, since that >> doesn’t >> >>> involve a massive effort. >> >>> >> >>> I’ve been meaning to do a little benchmarking and profiling for a while >> >>> now, and it seems like a f

Re: Why isn't there a separate JVM per table?

2018-02-22 Thread Nate McCall
I've heard a couple of folks pontificate on compaction in its own process as well, given it has such a high impact on GC. Not sure about the value of individual tables. Interesting idea though. On Fri, Feb 23, 2018 at 10:45 AM, Gary Dusbabek wrote: > I've given it some

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

2018-02-15 Thread Nate McCall
Thanks, Jason!! On Fri, Feb 16, 2018 at 1:18 PM, Jason Brown <jasedbr...@gmail.com> wrote: > Nate, I can do this. > > On Thu, Feb 15, 2018 at 2:51 PM, Nate McCall <zznat...@gmail.com> wrote: > >> > >> > My circleci test runs fail on lack of resources

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

2018-02-15 Thread Nate McCall
> > My circleci test runs fail on lack of resources and I understand now > that Jason used the circleci configuration from the trunk branch to run > the 3.0 and 3.11 branches. These branches should get commits for a > working CI configuration in-tree. > Quick follow up - does someone have an

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

2018-02-14 Thread 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

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

2018-02-14 Thread 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

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

2018-02-12 Thread Nate McCall
+1 Thanks for the reroll!! On Feb 13, 2018 4:41 PM, "Michael Shuler" wrote: > I propose the following artifacts for release as 3.11.2. > > sha1: 8a5e88f635fdb984505a99a553b5799cedccd06d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a= >

Re: [VOTE] Release Apache Cassandra 3.11.2

2018-02-12 Thread Nate McCall
I thought we had committed CASSANDRA-14212 last week. We need a release bad enough that I don't want to sink this with a -1, but we have seen this be an issue with folks a couple of times recently. On Tue, Feb 13, 2018 at 10:16 AM, Jon Haddad wrote: > I’m a +1 on getting

Re: [VOTE] Release Apache Cassandra 2.1.20

2018-02-12 Thread Nate McCall
> I propose the following artifacts for release as 2.1.20. > +1 - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 3.11.2

2018-02-12 Thread Nate McCall
> I propose the following artifacts for release as 3.11.2. > +1 - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 3.0.16

2018-02-12 Thread Nate McCall
> I propose the following artifacts for release as 3.0.16. > +1 - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: [VOTE] Release Apache Cassandra 2.2.12

2018-02-12 Thread Nate McCall
> I propose the following artifacts for release as 2.2.12. +1 - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: How to fetch replication factor of a given keyspace

2017-12-20 Thread Nate McCall
I think you want: Schema.instance.getKeyspaceMetadata There is a ReplicationParams nested under there which should have everything you need fully populated. On Thu, Dec 21, 2017 at 2:02 PM, Tyagi, Preetika wrote: > Hi, > > If I need to get the replication factor of a

Re: duration based config settings

2017-12-04 Thread Nate McCall
> I'd be in favour of never retiring the _ms format though - it's almost > free, there's no backward compatibility problems, and it's fairly intuitive > so long as we're consistent about it. > Agreed on this point. Overall, this will be excellent for usability.

Re: custom validation before replication

2017-11-16 Thread Nate McCall
On Fri, Nov 17, 2017 at 9:11 AM, Abdelkrim Fitouri wrote: > Trigger does not resolve my problem because it is not a format validation > issue but an integrity constraint ... > > My purpose is to check data integrity before replication, by returning an > error and killing the

Re: [VOTE] Release Apache Cassandra 3.0.15

2017-10-02 Thread Nate McCall
+1 On Tue, Oct 3, 2017 at 6:18 AM, Michael Shuler wrote: > I propose the following artifacts for release as 3.0.15. > > sha1: b32a9e6452c78e6ad08e371314bf1ab7492d0773 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/3.0.15-tentative >

Re: Expected release date for 3.11.1?

2017-09-28 Thread Nate McCall
Agree on waiting for SRP. And in general having the patience to put out artifacts in which we have higher confidence. Thanks for the effort Alexi. On Sep 29, 2017 5:29 AM, "Michael Shuler" wrote: > I'm happy to include these for the quality. Let's draw the line in the >

Re: [VOTE] Release Apache Cassandra 2.2.11

2017-09-28 Thread Nate McCall
+1 On Sep 29, 2017 7:41 AM, "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 >

Re: [VOTE] Release Apache Cassandra 2.1.19

2017-09-28 Thread Nate McCall
+1 On Sep 29, 2017 7:12 AM, "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:

Re: The future: Java 9 and the disappearance of CLASSPATH

2017-09-20 Thread Nate McCall
There are several other components that function similarly (compaction strategies, snitches, UDFs, etc.). I don't see us doing anything different without a compelling reason. On Thu, Sep 21, 2017 at 3:06 AM, Russell Bateman wrote: > We're very new to Cassandra. > > We

Should we do some releases?

2017-09-19 Thread Nate McCall
It's been about 3 mos since our last set. - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org

Re: State of Materialized Views

2017-07-24 Thread Nate McCall
> > We're working on the following MV-related issues in the 4.0 time-frame: > CASSANDRA-13162 > CASSANDRA-13547 Patch Available > CASSANDRA-13127 Patch Available > CASSANDRA-13409 Patch Available > CASSANDRA-12952 Patch Available > CASSANDRA-13069 > CASSANDRA-12888

Re: State of Materialized Views

2017-07-20 Thread Nate McCall
> > so perhaps the real solution is we need to be more aggressive about > nominating and electing committers who are willing to spend some attention on > MVs. > I am very much +1 on this solution. Huge thanks to Kurt for the excellent summarization and to Benjamin and ZhaoYang for all their

Cassandra dtest cloned to ASF

2017-07-12 Thread Nate McCall
https://github.com/apache/cassandra-dtest History is intact, but I left all the branches as that all looked like a bunch of one-off personal stuff. DataStax folks - what do y'all want to do re: "repository has moved" readme or similar? Tracking this under:

  1   2   3   >