Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Alex Lourie
Same here. I've been working on this project for a bit now, and I'm planning to continue and contribute. I also like the idea of this project becoming an officially endorsed golang Cassandra driver. Makes a lot of sense too. Alex. On Sat., 1 Sep. 2018, 01:08 Chris Bannister, wrote: > I

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Dinesh Joshi
> On Aug 31, 2018, at 4:06 PM, Michael Shuler wrote: > > Yep! I was going to comment similarly. I would be in full support of a > committer who focused purely on documentation and website content, for > instance. It's a matter of trusting a contributor to know what and where > to commit, as

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Michael Shuler
On 08/31/2018 05:20 PM, Brandon Williams wrote: > On Fri, Aug 31, 2018 at 4:24 PM Gary Dusbabek wrote: > >> At what point is the project comfortable/trusting with granting commit bits >> to someone who is very familiar with a facet of the project (say, a go >> client, or dtests), but hasn't made

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Brandon Williams
On Fri, Aug 31, 2018 at 4:24 PM Gary Dusbabek wrote: > It would also make sense to think about how existing maintainers are > brought in as committers, if appropriate (official vote, etc.). I'm under > the impression that Apache commit bits are granted in a binary fashion - > you have access to

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Gary Dusbabek
It would also make sense to think about how existing maintainers are brought in as committers, if appropriate (official vote, etc.). I'm under the impression that Apache commit bits are granted in a binary fashion - you have access to everything or nothing. <-- Is this incorrect? At what point is

Re: Transient Replication 4.0 status update

2018-08-31 Thread Carl Mueller
I see, so there are no dedicated transient nodes, just other nodes that function as witnesses. This is still very exciting. On Fri, Aug 31, 2018 at 1:49 PM Ariel Weisberg wrote: > Hi, > > All nodes being the same (in terms of functionality) is something we > wanted to stick with at least for

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread dinesh.jo...@yahoo.com.INVALID
I like the idea of having an officially supported Go Driver under ASF. It would mean easier contributions. I don't think we should necessarily limit it to a reference implementation. The industry has a strong interest in building server side as well as client software in Go. Dinesh On

Re: Transient Replication 4.0 status update

2018-08-31 Thread Ariel Weisberg
Hi, All nodes being the same (in terms of functionality) is something we wanted to stick with at least for now. I think we want a design that changes the operational, availability, and consistency story as little as possible when it's completed. Ariel On Fri, Aug 31, 2018, at 2:27 PM, Carl

Re: Transient Replication 4.0 status update

2018-08-31 Thread Ariel Weisberg
Hi, There are no transient nodes. All nodes are the same. If you have transient replication enabled each node will transiently replicate some ranges instead of fully replicating them. Capacity requirements are reduced evenly across all nodes in the cluster. Nodes are not temporarily transient

Re: Transient Replication 4.0 status update

2018-08-31 Thread Carl Mueller
SOrry to spam this with two messages... This ticket is also interesting because it is very close to what I imagined a useful use case of RF4 / RF6: being basically RF3 + hot spare where you marked (in the case of RF4) three nodes as primary and the fourth as hot standby, which may be equivalent

Re: Transient Replication 4.0 status update

2018-08-31 Thread Carl Mueller
I put these questions on the ticket too... Sorry if some of them are stupid. So are (basically) these transient nodes basically serving as centralized hinted handoff caches rather than having the hinted handoffs cluttering up full replicas, especially nodes that have no concern for the token

Re: Java 11 Z garbage collector

2018-08-31 Thread Jeff Jirsa
Read heavy workload with wider partitions (like 1-2gb) and disable the key cache will be worst case for GC -- Jeff Jirsa > On Aug 31, 2018, at 10:51 AM, Carl Mueller > wrote: > > I'm assuming that p99 that Rocksandra tries to target is caused by GC > pauses, does anyone have data

Re: Java 11 Z garbage collector

2018-08-31 Thread Carl Mueller
I'm assuming that p99 that Rocksandra tries to target is caused by GC pauses, does anyone have data patterns or datasets that will generate GC pauses in Cassandra to highlight the abilities of Rocksandra (and... Scylla?) and perhaps this GC approach? On Thu, Aug 30, 2018 at 8:11 PM Carl Mueller

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Jason Brown
I find this idea interesting and worth a strong discussion. Something to consider is an argument floating around in the admin tool/side car discussion: if we take an existing project wholesale, we inherit all of it's design decision and technical debt (every project has these). On the other hand,

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Chris Bannister
I intend to stay on and continue to contribute. On Fri, 31 Aug 2018 at 4:37 pm, Jonathan Ellis wrote: > On Fri, Aug 31, 2018 at 9:14 AM Nate McCall wrote: > > > Hi folks, > > So I was recently talking with, Chris Bannister the gocql [0] > > maintainer, and he expressed an interest in donating

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Jonathan Ellis
On Fri, Aug 31, 2018 at 9:14 AM Nate McCall wrote: > 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. > Is he looking to continue to maintain it or is he looking to give it a good home when

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Jonathan Haddad
Definitely does not belong in the same repo. I’m all for folding drivers in / writing our own, just needs active committers. On Fri, Aug 31, 2018 at 7:45 AM Michael Shuler wrote: > On 08/31/2018 09:34 AM, Jay Zhuang wrote: > > That's great. Could that be in the same repo as Cassandra or a > >

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Sumanth Pasupuleti
It sounds great to have an official GoCQL driver. I like the mentioned end goal of having a reference implementation that evolves with the core C* project. Thanks, Sumanth On Fri, Aug 31, 2018 at 7:45 AM Michael Shuler wrote: > On 08/31/2018 09:34 AM, Jay Zhuang wrote: > > That's great.

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Michael Shuler
On 08/31/2018 09:34 AM, Jay Zhuang wrote: > That's great. Could that be in the same repo as Cassandra or a > separate repo? For similar reasons as discussed for an admin tool, separate repositories are quick and simple to create, as well as allow handling contribution, CI, build, release, etc.

Re: NGCC 2018?

2018-08-31 Thread Jay Zhuang
Are we going to have a dev event next month? Or anything this year? We may also be able to provide space in bay area and help to organize it. (Please let us know, so we could get final approval for that). On Fri, Jul 27, 2018 at 10:05 AM Jonathan Haddad wrote: > My interpretation of Nate's

Re: [Discuss] Accept GoCQL driver donation

2018-08-31 Thread Jay Zhuang
That's great. Could that be in the same repo as Cassandra or a separate repo? On Fri, Aug 31, 2018 at 7:14 AM Nate McCall wrote: > 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

[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