Re: counterpart to HBase's coprocessors.

SOME lightweight processing is possible with UDFs / UDAs: http://www.planetcassandra.org/blog/user-defined-functions-in-cassandra-3-0 / They're not directly comparable to Hbase coprocessors, but they allow some computation on the server. On 12/10/15, 11:02 PM, "hongbin ma"

Re: Cassandra Java Driver and DataStax

https://github.com/hector-client/hector https://github.com/Netflix/astyanax http://doanduyhai.github.io/Achilles/ https://github.com/noorq/casser https://github.com/impetus-opensource/Kundera https://github.com/deanhiller/playorm - Jeff ( Not affiliated with datastax ) On 6/3/16,

Re: How cassandra ensures consistency when adding or removing a node?

https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/locator/TokenMetadata.java#L731-L754 And https://github.com/apache/cassandra/blob/trunk/src/java/org/apache/cassandra/locator/TokenMetadata.java#L60-L88 Cassandra keeps a map of joining and leaving nodes, and does

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

+1 (nonbinding) to at least announcing major architectural improvements on dev email. I don’t know that it’s going to help encourage more contributors like Chris suggests, but it seems like at worst it won’t hurt, and certainly should help make people aware of Jiras that would otherwise slip

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

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 created, we send an email to both dev@ and >issues@. This will be an extra 40 emails per month on the dev list. I am

Re: Performance issue in 3.0.9

Can you quantify "major"? Latency or throughput? GC pauses? What did you see before? What do you see now? Do you have a stack dump? -- Jeff Jirsa > On Feb 1, 2017, at 4:23 PM, Shashank Joshi <shashank.jo...@ericsson.com> > wrote: > > We are seeing major perfo

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

+1 -- Jeff Jirsa > On Jan 31, 2017, at 1:29 PM, Michael Shuler <mich...@pbandjelly.org> wrote: > > I propose the following artifacts for release as 3.10. > > sha1: 3cf415279c171fe20802ad90f181eed7da04c58d > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra

Re: Pluggable throttling of read and write queries

On 2017-02-20 22:47 (-0800), Benjamin Roth wrote: > Thanks. > > Depending on the whole infrastructure and business requirements, isn't it > easier to implement throttling at the client side? > I did this once to throttle bulk inserts to migrate whole CFs from other >

Re: Pluggable throttling of read and write queries

On 2017-02-17 18:12 (-0800), Abhishek Verma wrote: > > > Is there a way to throttle read and write queries in Cassandra currently? > If not, what would be the right place in the code to implement a pluggable > interface for doing it. I have briefly considered using triggers,

Re: Pluggable throttling of read and write queries

On 2017-02-20 21:35 (-0800), Benjamin Roth wrote: > Stupid question: > Why do you rate limit a database, especially writes. Wouldn't that cause a > lot of new issues like back pressure on the rest of your system or timeouts > in case of blocking requests? > Also rate

Re: [VOTE] Release Apache Cassandra 2.1.17

+1 On Wed, Feb 15, 2017 at 5:23 PM, Jason Brown wrote: > +1 > > On Wed, Feb 15, 2017 at 5:16 PM, Michael Shuler > wrote: > > > I propose the following artifacts for release as 2.1.17. > > > > sha1: 943db2488c8b62e1fbe03b132102f0e579c9ae17 > > Git:

Re: [VOTE] Release Apache Cassandra 3.0.11

+1 On Wed, Feb 15, 2017 at 5:24 PM, Jason Brown wrote: > +1 > > On Wed, Feb 15, 2017 at 5:15 PM, Michael Shuler > wrote: > > > I propose the following artifacts for release as 3.0.11. > > > > sha1: 338226e042a22242645ab54a372c7c1459e78a01 > > Git:

Re: [VOTE] Release Apache Cassandra 2.2.9

+1 On Wed, Feb 15, 2017 at 5:24 PM, Jason Brown wrote: > +1 > > On Wed, Feb 15, 2017 at 5:16 PM, Michael Shuler > wrote: > > > I propose the following artifacts for release as 2.2.9. > > > > sha1: 70a08f1c35091a36f7d9cc4816259210c2185267 > > Git: >

Re: #cassandra-dev IRC logging

st want to make sure I'm >> >>>> understanding correctly :) ) >> >>>> >> >>>> On Fri, Aug 26, 2016 at 12:28 PM, Edward Capriolo >> >>>> <edlinuxg...@gmail.com >> >>>> >> >>>> wrote: >> >&g

Re: Proposal - 3.5.1

get this, and startup will fail: >>>> >>>> ERROR 05:32:09 Exiting due to error while processing commit log during >>>> initialization. >>>> org.apache.cassandra.db.commitlog.CommitLogReplayer$CommitLogReplayException: >>>> Unexpected error deserializing mutation; saved to >

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

On 9/9/16, 5: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. > >There seems no way to change the number of vnodes on

Re: [VOTE] Release Apache Cassandra 2.2.8

+1 On 2016-09-23 16:04 (-0700), 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 >

Re: [VOTE] Release Apache Cassandra 3.9

+1 On 2016-09-26 08:12 (-0700), 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 >

Re: [VOTE] Release Apache Cassandra 3.8

+1 On 2016-09-26 07:52 (-0700), 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 >

Re: [VOTE] Release Apache Cassandra 2.1.16

+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

Re: Proprietary Replication Strategies: Cassandra Driver Support

That sounds awful, especially since you could just use SimpleStrategy with RF=1 and then bootstrap / decom would handle resharding for you as expected. -- Jeff Jirsa > On Oct 8, 2016, at 10:09 AM, Edward Capriolo <edlinuxg...@gmail.com> wrote: > > I have contemplated usin

Re: Proprietary Replication Strategies: Cassandra Driver Support

I'm sure that's what he meant, I just disagree that it sounds useful -- Jeff Jirsa > On Oct 8, 2016, at 10:33 AM, Vladimir Yudovin <vla...@winguzone.com> wrote: > > As far as I understand Edward meant to have option determinate actual storage > node on client side, by dr

Re: Proposal - 3.5.1

We did 3.1.1 and 3.2.1, so there’s SOME precedent for emergency fixes, but we certainly didn’t/won’t go back and cut new releases from every branch for every critical bug in future releases, so I think we need to draw the line somewhere. If it’s fixed in 3.7 and 3.0.x (x >= 6), it seems like

Re: Hints handoff is memory intensive

that parnew pause. -- Jeff Jirsa > On Sep 19, 2016, at 11:12 PM, Dikang Gu <dikan...@gmail.com> wrote: > > In our 2.1 cluster, I find that hints handoff is using a lot of memory on > our proxy nodes, when delivering hints to a data node that was dead for 3+ > hours (

Re: #cassandra-dev IRC logging

+1 to both as well On 8/26/16, 11:59 AM, "Tyler Hobbs" wrote: >+1 on doing this and using ASFBot in particular. > >On Fri, Aug 26, 2016 at 1:40 PM, Jason Brown wrote: > >> @Dave ASFBot looks like a winner. If others are on board with this, I can >>

#cassandra-dev IRC logging

There exists a #cassandra-dev IRC channel that’s historically been used by developers discussing the project – while it’s public, it’s not archived, and it’s not a mailing list. The ASF encourages all discussion to be archived, and ideally, archived on a public mailing list. Jake

Re: Github pull requests

I guess someone would have to open 3 different PRs (say, 2.2, 3.0, trunk), and the committer would have 3 different commit messages to close each of them? Anyone have examples of projects with branching strategies similar to ours using github pull requests? On 8/29/16, 6:26 AM, "Sylvain

Re: [VOTE] Accept dtests Donation Into Project

+1 -- Jeff Jirsa > On Sep 30, 2016, at 11:51 AM, Nate McCall <zzn...@apache.org> 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 disc

Re: DataStax role in Cassandra and the ASF

Now that I have clarity on what can and can't be relayed to the community / dev@, I'm going to reply to this email, and then I suspect I'm done for today, because I'd rather watch football than reply to this anymore. On Sat, Nov 5, 2016 at 6:30 AM, Mark Struberg

Re: DataStax role in Cassandra and the ASF

My first reaction to seeing this come in was to laugh - not because it's funny, but because the only other thing I could think to do was cry. You've misinterpreted or misunderstood almost everything in this post, and instead of reflecting on your side of the interaction, you've attributed the

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

There exists a nearly unused mailing list, client-...@cassandra.apache.org [0]. This is a summary of the email threads over the past 12 months on that list: 1) ApacheCon Seville CFP Close notice 2) Datastax .NET driver question 3) Datastax Java driver question 4) FOSDEM announce 5) ApacheCon

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

-1 as well, #12877 On 11/9/16, 5:20 AM, "Oleksandr Petrov" wrote: >-1 > >Sorry but I have to -1 that one, with the following explanation > >One of the features in 3.10 breaks SASI in quite a significant way. The >issue was introduced in #11990 [1] and described in

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

With 8 binding +1s (including myself), 3 non-binding +1, and no -1, the vote passes, and we'll work to close out this list. - Jeff On 2016-11-06 21:11 (-0800), "Jeff Jirsa"<jji...@apache.org> wrote: > There exists a nearly unused mailing list, client-...@cassand

Re: Rough roadmap for 4.0

Also https://issues.apache.org/jira/browse/CASSANDRA-12676 -- Jeff Jirsa > On Nov 4, 2016, at 11:51 AM, Jason Brown <jasedbr...@gmail.com> wrote: > > +1 to epaxos > >> On Fri, Nov 4, 2016 at 11:40 AM, Jonathan Haddad <j...@jonhaddad.com> wrote: >> >

Re: Broader community involvement in 4.0 (WAS Re: Rough roadmap for 4.0)

‘Accepted’ JIRA status seems useful, but would encourage something more explicit like ‘Concept Accepted’ or similar to denote that the concept is agreed upon, but the actual patch itself may not be accepted yet. /bikeshed. On 11/7/16, 2:56 AM, "Ben Slater" wrote:

Re: DataStax role in Cassandra and the ASF

Note also the work on https://issues.apache.org/jira/browse/CASSANDRA-9459 , reaching out to other “competitors” before major versions to ensure compatibility and awareness. I think there’s a ton of evidence supporting the assertion that datastax-employed committers and PMC members acted in

Re: Review of Cassandra actions

I hope the other 7 members of the board take note of this response, and other similar reactions on dev@ today. When Datastax violated trademark, they acknowledged it and worked to correct it. To their credit, they tried to do the right thing. When the PMC failed to enforce problems, we

Re: DataStax role in Cassandra and the ASF

I agree - thanks for sending it, Lukasz. I think we can use it as a great learning opportunity - because nearly every point you made I find to be factually and objectively wrong, and the fact that members of the ASF take it at face value is part of the problem - poorly informed opinions on

Re: DataStax role in Cassandra and the ASF

thank them. As a member of the PMC, I encourage people to try to become more involved. It's a complicated piece of software, but it drives many of our businesses, and it will certainly live on. Best, Jeff Jirsa > On Nov 3, 2016, at 8:44 PM, Kelly Sommers <kell.somm...@gmail.com> wrote: > &

Re: Proposal - 3.5.1

On 2016-10-20 14:21 (-0700), Jeremiah Jordan wrote: > In the original tick tock plan we would not have kept 4.0.x around. So I am > proposing a change for that and then we label the 3.x and 4.x releases as > "development releases" or some other thing and have "yearly"

Re: Proposal - 3.5.1

On 2016-10-20 13:26 (-0700), "J. D. Jordan" wrote: > If you think of the tick tock releases as interim development releases I > actually think they have been working pretty well. What if we continue with > the same process and do 4.0.x as LTS like we have 3.0.x

Re: Low hanging fruit crew

Let’s not get too far in the theoretical weeds. The email thread really focused on low hanging tickets – tickets that need review, but definitely not 8099 level reviews: 1) There’s a lot of low hanging tickets that would benefit from outside contributors as their first-patch in Cassandra (like

Re: Status of dtest donation?

Incubator handles the ICLA / IP transfer for the subrepo. On 11/21/16, 10:11 AM, "Jonathan Ellis" wrote: >I thought we could just pull dtest into another repo managed by C* PMC. Do >we need to involve incubator? > >On Mon, Nov 21, 2016 at 11:50 AM, Nate McCall

Re: STCS in L0 behaviour

Without yet reading the code, what you describe sounds like a reasonable optimization / fix, suitable for 3.0+ (probably not 2.2, definitely not 2.1) -- Jeff Jirsa > On Nov 23, 2016, at 7:52 AM, Marcus Olsson <marcus.ols...@ericsson.com> wrote: > > Hi everyone, > &g

Re: STCS in L0 behaviour

What you’re describing seems very close to what’s discussed in   https://issues.apache.org/jira/browse/CASSANDRA-10979 - worth reading that ticket a bit. There does seem to be a check for STCS in L0 before it tries higher levels:

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

+1 On 2016-11-18 10:08 (-0800), 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 >

Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)

We should assume that we’re ditching tick/tock. I’ll post a thread on 4.0-and-beyond here in a few minutes. The advantage of a prod release every 6 months is fewer incentive to push unfinished work into a release. The disadvantage of a prod release every 6 months is then we either have a very

Proposals for releases - 4.0 and beyond

With 3.10 voting in progress (take 3), 3.11 in December/January (probably?), we should solidify the plan for 4.0. I went through the archives and found a number of proposals. We (PMC) also had a very brief chat in private to make sure we hadn’t missed any, and here are the proposals that we’ve

Re: Rough roadmap for 4.0

We’ll be voting in the very near future on timing of major releases and release strategy. 4.0 won’t happen until that vote takes place. But since you asked, I have ONE tick/tock (3.9) cluster being qualified for production because it needs SASI. - Jeff On 11/17/16, 9:59 AM, "Jonathan

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

+1 -- Jeff Jirsa > On Nov 11, 2016, at 5:36 PM, Michael Shuler <mich...@pbandjelly.org> wrote: > > I propose the following artifacts for release as 3.0.10. > > sha1: d6a3ef4863142c3f9fc1def911f28341fc78f2e8 > Git: > http://git-wip-us.apache.org/repos/asf?p=cass

Re: Summary of 4.0 Large Features/Breaking Changes (Was: Rough roadmap for 4.0)

Any proposal to solve the problem you describe? -- Jeff Jirsa > On Nov 19, 2016, at 8:50 AM, Edward Capriolo <edlinuxg...@gmail.com> wrote: > > This is especially relevant if people wish to focus on removing things. > > For example, gossip 2.0 sounds great, but see

Re: [VOTE] Release Apache Cassandra 3.0.10

-1 , regression On 11/2/16, 1:52 PM, "Nate McCall" wrote: >[Copied from 3.10 thread] >Sorry all. Changing my vote to -1 per my comment:

Re: [VOTE] Release Apache Cassandra 3.10

-1, regression On 2016-10-31 08:18 (-0700), Michael Shuler wrote: > I propose the following artifacts for release as 3.10. > > sha1: a3828ca8b755fc98799867baf07039f7ff53be05 > Git: >

Re: CASSANDRA-8596

. -- Jeff Jirsa > On Nov 29, 2016, at 12:19 AM, Vladimir Yudovin <vla...@winguzone.com> wrote: > > Hi, > > > > in the light of broader community involvement I would like to bring > attentions to the https://issues.apache.org/jira/browse/CASSANDRA-8596 I open > wit

Re: Current Branch Merge Path - PLEASE READ!

It depends on severity, but generally… If you find a bug in 3.0, you should work back to 2.1 to see if it exists in older versions. We don’t put minor fixes into 2.1 (or really 2.2 at this point) – 2.1 is critical fixes only, and 2.2 is getting to that point as well. If it’s a minor minor bug,

Re: Wrapping up tick-tock

Mick proposed it (semver) in one of the release proposals, and I dropped the ball on sending out the actual "vote on which release plan we want to use" email, because I messed up and got busy. On Fri, Jan 13, 2017 at 11:26 AM, Russell Bradberry wrote: > Has any thought

Re: [VOTE] 3.X branch feature freeze

+1 On Fri, Jan 13, 2017 at 10:52 AM, Josh McKenzie wrote: > +1 > > On Fri, Jan 13, 2017 at 1:43 PM, Blake Eggleston > wrote: > > > +1 > > > > > > On January 13, 2017 at 12:38:55 PM, Michael Shuler ( > mich...@pbandjelly.org) > > wrote: > > > > +1 to

Re: Per blockng release on dtest

+1 On Tue, Jan 10, 2017 at 9:23 AM, Aleksey Yeschenko wrote: > That’s a good point. > > So 3.11 after 3.10, then move on to 3.11.x further bug fix releases? > > +1 to that. > > -- > AY > > On 10 January 2017 at 17:22:09, Michael Shuler (mich...@pbandjelly.org) > wrote: > >

Re: Where do I find EverywhereStrategy?

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/browse/CASSANDRA-12629 but no > reason has been given why... > It's touched on in that thread, but

Re: Collecting slow queries

Should we reopen 6226? Tracing 0.1% doesn’t help find the outliers that are slow but don’t time out (slow query log could help find large partitions for users with infrequent but painful large partitions, far easier than dumping sstables to json to identify them). On 12/5/16, 1:28 PM,

Re: Collecting slow queries

That’s great. I had no idea that ticket existed. On 12/5/16, 1:41 PM, "Yoshi Kimoto" <yy.kim...@gmail.com> wrote: >This? : https://issues.apache.org/jira/browse/CASSANDRA-12403 > >2016-12-06 6:36 GMT+09:00 Jeff Jirsa <jeff.ji...@crowdstrike.com>: > >> Sho

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

+1 -- Jeff Jirsa > On Jan 13, 2017, at 4:46 PM, Michael Shuler <mich...@pbandjelly.org> wrote: > > I propose the following artifacts for release as 3.10. > > sha1: 9c2ab25556fad06a6a4d58f4bb652719a8a1bc27 > Git: > http://git-wip-us.apache.org/repos/asf?p=cassandra

Re: SSTable Ancestors information in Cassandra 3.0.x

That information was removed, because it was really meant to be used for a handful of internal tasks, most of which were no longer used. The remaining use was cleaning up compaction leftovers, and the compaction leftover code was rewritten in 3.0 / CASSANDRA-7066 (note, though, that it's somewhat

Re: SSTable Ancestors information in Cassandra 3.0.x

nal tasks and the compaction tasks move to a > timestamp-based approach? > > Regards, > Rajath > > > Rajath Subramanyam > > > On Thu, Mar 23, 2017 at 2:12 PM, Jeff Jirsa <jji...@gmail.com> wrote: > > > That information was removed, beca

Re: DataStax Client List

The original email and this reply are totally inappropriate. At best, this is a wholly invalid use of the list to peddle fake contact lists. At worst, it's inappropriately disseminating a list that's likely covered under NDA. I'll be unsubscribing any user who continues to humor this poster

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

With 6 binding +1s, 6 non-binding +1s, and no -1s of any kind, the vote passes, I'll ask for a new mailing list and get this transitioned. - Jeff On 2017-03-20 15:32 (-0700), Jeff Jirsa <jji...@gmail.com> wrote: > There's no reason for the dev list to get spammed everytime there's a

Weekly Cassandra Status

Email stuff: - We've moved github pull requests notifications from dev@ to pr@ - if you want to see when github issues are opened or updated, subscribe to the new list (send email to pr-subscr...@cassandra.apache.org ), or check out the archives at

Re: [VOTE] self-assignment of jira tickets

+1 -- Jeff Jirsa > On Mar 29, 2017, at 6:21 AM, Jason Brown <jasedbr...@gmail.com> wrote: > > Hey all, > > Following up my thread from a week or two ago ( > https://lists.apache.org/thread.html/0665f40c7213654e99817141972c003a2131aba7a1c63d6765db75c5@%3Cdev.cassand

Re: thread architecture of Cassandra

Hi Suli, Attachments to mailing lists often get filtered - can you paste it online and send a link? - Jeff On Wed, Mar 22, 2017 at 1:10 PM, 杨苏立 Yang Su Li wrote: > Hi, > > I am a graduate student working on scheduling on storage systems, and we > are interested in how

Proposal: push TravisCI and CircleCI yaml files into the active branches

To further our recent conversations on testing, I've opened the following JIRA: https://issues.apache.org/jira/browse/CASSANDRA-13388 This should allow us to do SOME amount of automated testing for developers without jumping through a ton of hoops. If the free plans prove to be insufficient, we

Re: Documentation contributors guide

On 2017-03-17 13:06 (-0700), benjamin roth wrote: > Isn't there a way to script that with just a few lines of python or > whatever? For docs, probably. Real patches are harder. There's a minor problem that they're a bit spammy (all PRs create dev@ emails), but I'd rather

Re: Documentation contributors guide

> > On 2017-03-17 12:33 (-0700), Stefan Podkowinski wrote: > > > >> As you can see there's a large part about using GitHub for editing on > >> the page. I'd like to know what you think about that and if you'd agree > >> to accept PRs for such purposes. I don't want to bury the

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

t; 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 though. > >> > >> On March 20, 2017 at 3:00:47 PM, Jeff Jirsa (jji...@gmail.com) wrote: > >> > >> There's no reason

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

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 ( see https://issues.apache.org/jira/browse/CASSANDRA-13256 ,

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

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 ( see https://issues.apache.org/jira/browse/CASSANDRA-13256 ,

Re: Documentation contributors guide

On 2017-03-17 12:33 (-0700), Stefan Podkowinski wrote: > As you can see there's a large part about using GitHub for editing on > the page. I'd like to know what you think about that and if you'd agree > to accept PRs for such purposes. > The challenge of github PRs isn't

Weekly Cassandra Topics Of Interest Thread

Another week, another quick summary of topics of interest (to me) as we close out the Feast of Saint Patrick. As before, if you feel you have something that you feel needs more eyeballs, please reply and add it. Don't be shy. A few significant mailing list threads: - We've talked a lot about

Re: Code quality, principles and rules

On 2017-03-16 10:32 (-0700), François Deliège wrote: > > To get this started, here is an initial proposal: > > Principles: > > 1. Tests always pass. This is the starting point. If we don't care about > test failures, then we should stop writing tests. A recurring

Re: jira ticket assignment

Based on Jason's the INFRA jira ( https://issues.apache.org/jira/browse/INFRA-11950 ) , it looks like we can remove the blocker if desired - does anyone have any argument for keeping it? Or should we just jump to a vote? On Tue, Mar 14, 2017 at 4:59 PM, Jonathan Ellis wrote:

Re: Weekly Cassandra Wrap-up

On Sun, Apr 2, 2017 at 7:53 PM, Jeff Jirsa <jji...@gmail.com> wrote: > 3) As a follow-up to #2, I proposed pushing up some CircleCI and Travis > YML files into the active branches to make testing easier - ( > https://lists.apache.org/thread.html/48e73ff0d2aff5a

Re: Weekly Cassandra Wrap-up

a more comprehensive list of these third party tools and include them in the docs - are there any tools you find useful in using Cassandra that should be listed? On Sun, Apr 2, 2017 at 7:53 PM, Jeff Jirsa <jji...@gmail.com> wrote: > From the email list: > > 1) Some grad students

Re: [VOTE] Release Apache Cassandra 3.0.13

+1 -- Jeff Jirsa > On Apr 11, 2017, at 11:59 AM, Michael Shuler <mich...@pbandjelly.org> wrote: > > I propose the following artifacts for release as 3.0.13. > > sha1: 91661ec296c6d089e3238e1a72f3861c449326aa > Git: > http://git-wip-us.apache.org/repos/asf?p=cass

Re: Cassandra on RocksDB experiment result

Let's try to make this actionable. Long time contributors/committers/members of the PMC (especially you guys who have been working on internals for 4-8 years): Setting aside details of the implementation, does anyone feel that pluggable storage in itself is inherently a bad idea (so much so that

Re: committing performance patches without performance numbers

Agree. Anything that's meant to increase performance should demonstrate it actually does that. We have microbench available in recent versions - writing a new microbenchmark isn't all that onerous. Would be great if we had perf tests included in the normal testall/dtest workflow for ALL patches so

Re: State of triggers

On Fri, Mar 3, 2017 at 5:40 AM, Edward Capriolo wrote: > > I used them. I built do it yourself secondary indexes with them. They have > there gotchas, but so do all the secondary index implementations. Just > because datastax does not write about something. Lets see like 5

Re: Consistent vs inconsistent range movements

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. Some time later, node 2 comes online. Then you want to add node 2.5 in between nodes 1 and 3. If you stream data from node 2, you violate consistency guarantees (quorum) -

Re: Consistent vs inconsistent range movements

ar 3, 2017 at 5:44 PM, Jeff Jirsa <jji...@gmail.com> 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. > > > > Some time later, node 2 comes online. > > > > Then you wa

Re: State of triggers

> On Mar 4, 2017, at 7:06 AM, Edward Capriolo <edlinuxg...@gmail.com> wrote: > >> On Fri, Mar 3, 2017 at 12:04 PM, Jeff Jirsa <jji...@gmail.com> wrote: >> >> On Fri, Mar 3, 2017 at 5:40 AM, Edward Capriolo <edlinuxg...@gmail.com> >> wrote:

Re: How can I scale my read rate?

5.5G of ram isn't very much for a jvm based database. Having fewer instances with more ram will likely give you better performance. Also, this is probably a better question for the user list than the Dev list -- Jeff Jirsa > On Mar 11, 2017, at 1:20 PM, S G <sg.online.em...@gmail.com&

Hopefully Weekly Apache Cassandra JIRA Topics of Interest

Hi folks, Cassandra JIRA is huge, active, and ever-changing. It's easy to miss tickets you may care about, or if you want to start contributing, sometimes it's hard to know where to start. I'm going to make an attempt to pick a few dozen JIRAs each week (or month?) that would benefit from some

Re: Contribute to the Cassandra wiki

We're trying to use the in-tree docs. Those are preferred, updating the wiki is OK, but the wiki is VERY out of date. -- Jeff Jirsa > On Mar 12, 2017, at 3:21 PM, Long Quanzheng <prc...@gmail.com> wrote: > > Is the wiki still being used? > https://wiki.apache.or

Re: State of triggers

As far as I know, I've never met anyone who wrote and used their own triggers in production. I imagine the number of people doing so is very small, regardless of version. On Thu, Mar 2, 2017 at 11:04 AM, S G wrote: > Hi, > > I am not able to find any documentation on

Re: [VOTE] Release Apache Cassandra 3.0.12

+1 On Tue, Mar 7, 2017 at 10:06 AM, Michael Shuler wrote: > On 03/07/2017 10:15 AM, Michael Shuler wrote: > > The vote will be open for 72 hours (longer if needed). > > I'd like to amend this vote to be 48 hours, if there are no complaints > with this timeframe. > > --

Re: CASSANDRA-9472 Reintroduce off heap memtables - patch to 3.0

On 2017-07-29 10:02 (-0700), Jay Zhuang wrote: > Should we consider back-porting it to 3.0 for the community? I think > this is a performance regression instead of new feature. And we have the > feature in 2.1, 2.2. > Personally / individually, I'd much rather

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

I'll open an infra ticket. -- Jeff Jirsa > On Jul 28, 2017, at 7:28 AM, Aleksey Yeschenko <alek...@apache.org> wrote: > > +1 > > — > AY > > On 28 July 2017 at 11:47:29, Stefan Podkowinski (s...@apache.org) wrote: > > Can we forward notificati

Re: TWCS High Disk Space Usage Troubleshooting - Looking for suggestions

Looks a lot like read repair but impossible to tell for sure -- Jeff Jirsa > On Aug 9, 2017, at 4:34 PM, Sumanth Pasupuleti > <sumanth.pasupuleti...@gmail.com> wrote: > > My final try on pushing the attachment over. > > > ​ > >> On Wed, Aug 9,

Re: rebuild constantly fails, 3.11

On 2017-08-08 01:00 (-0700), Micha wrote: > Hi, > > it seems I'm not able to add add 3 node dc to a 3 node dc. After > starting the rebuild on a new node, nodetool netstats show it will > receive 1200 files from node-1 and 5000 from node-2. The stream from > node-1

Re: State of Materialized Views

On 2017-07-16 21:22 (-0700), kurt greaves wrote: > wall of text inc. > *tl;dr: *Aiming to come to some conclusions about what we are doing with > MV's and how we are going to make them stable in production. But really > just trying to raise awareness/involvement for MV's.

Re: Customize Cassandra to execute a query multiple times

On 2017-07-26 22:19 (-0700), Ke Wang wrote: > Hello all, > > Is there a way to customize Cassandra to execute a query multiple times? > There's always a way... > My use case is the following. When the Cassandra server receives queries > from remote clients, besides

Re: CASSANDRA-9472 Reintroduce off heap memtables - patch to 3.0

This is after you backported 9472 to 3.0? -- Jeff Jirsa > On Jul 27, 2017, at 10:33 PM, Andrew Whang <andrewgwh...@gmail.com> wrote: > > Jay, > > We see ~20% write latency improvement on 3.0.13 in a write-heavy workload, > using offheap_objects. offheap_buff

  1   2   3   4   >