Re: Harry in-tree (Forked from "Long tests, Burn tests, Simulator tests, Fuzz tests - can we clarify the diffs?")

+1, thank you for your efforts in bringing Harry in-tree. Anything that improves the testing ecosystem for Cassandra, particularly around complex scenarios / edge cases goes a long way in improving reliability, and with having a powerful tool like Harry in-tree, it is a lot more accessible to the

Re: [VOTE] Accept java-driver

+1 (nb) Thank you to everyone involved for reaching this point. Looking forward!! On Tue, Oct 3, 2023 at 8:19 AM Francisco Guerrero wrote: > +1 (nb) > > On 2023/10/03 14:51:04 Joseph Lynch wrote: > > +1 (nb) > > > > I am so grateful for all the hard work that went into getting the java > >

Re: Welcome Anthony Grasso, Erick Ramirez and Lorina Poland as Cassandra committers

Congratulations!!! On Wed, Feb 16, 2022 at 2:48 PM Joseph Lynch wrote: > Woo > > Congratulations to the new committers and I am so excited to see the > project recognizing these contributions! > > -Joey > > > On Tue, Feb 15, 2022 at 10:13 AM Benjamin Lerer wrote: > > > > The PMC members are

Re: [VOTE] CEP-3: Guardrails

+1 On Thu, Nov 11, 2021 at 6:10 AM Gary Dusbabek wrote: > +1 > > On Thu, Nov 11, 2021 at 5:30 AM Andrés de la Peña > wrote: > > > Hi everyone, > > > > I would like to start a vote on this CEP. > > > > Proposal: > > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-3%3A+Guardrails > >

Re: [DISCUSS] Creating a new slack channel for newcomers

+1 that existing channels of communication (cassandra-dev slack and mailing lists) should ideally suffice, and I have not seen prohibitive communication in those forums thus far that goes against newcomers. I agree it can be intimidating, but to Bowen's point, the more traffic we see around

Re: [VOTE] CEP-15: General Purpose Transactions

1. +1 nb 2. +1 nb 3. +1 nb Very excited about the possibilities this CEP will open up. Thanks for putting this together, Benedict. On Thu, Oct 14, 2021 at 2:08 PM Mick Semb Wever wrote: > > > > 1. Do you support adopting this CEP? > > 2. Do you support the transaction semantics proposed by the

Re: Welcome Aleksei Zotov as Cassandra committer

Congratulations Aleksei!! On Tue, Sep 21, 2021 at 5:39 AM Joshua McKenzie wrote: > Congrats Aleksei! > > > On Tue, Sep 21, 2021 at 7:51 AM Jonathan Ellis wrote: > > > Congratulations, Aleksei! > > > > On Tue, Sep 21, 2021 at 3:55 AM Benjamin Lerer > wrote: > > > > > The PMC members are

Re: [VOTE] CEP-13: Denylisting partitions

he.org > > > wrote: > > > > > +1 > > > > > > From: Brandon Williams > > > Date: Wednesday, 8 September 2021 at 17:57 > > > To: dev@cassandra.apache.org > > > Subject: Re: [VOTE] CEP-13: Denylisting partitions > > &

[VOTE] CEP-13: Denylisting partitions

Hi everyone, I’m proposing this CEP for approval. Proposal: https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-13%3A+Denylisting+partitions Discussion: https://lists.apache.org/thread.html/r1547c5f2fb8548e2f7dcbe1a26da8c2a95ebec81adeeb2ea0545924d%40%3Cdev.cassandra.apache.org%3E The vote

Re: [DISCUSS] CEP-13: Denylisting partitions

t; out comment threads on the design doc that are closed so we can see if > there's any outstanding discussions from a high level? > > ~Josh > > On Mon, Aug 30, 2021 at 1:14 AM Sumanth Pasupuleti < > sumanth.pasupuleti...@gmail.com> wrote: > > > +1. Made change

Re: [VOTE] Release Apache Cassandra 4.0.1

+1 nb Verified j8 unit tests and dtests pass https://app.circleci.com/pipelines/github/sumanth-pasupuleti/cassandra/98/workflows/52d8cd3f-0062-407e-a3f8-f78935cff0d4 On Wed, Sep 1, 2021 at 10:23 AM Andrés de la Peña wrote: > +1 > > On Wed, 1 Sept 2021 at 17:37, Ekaterina Dimitrova

Re: [DISCUSS] CEP-13: Denylisting partitions

e at a guardrail limit) > > So yeah, at least to me at face value it seems like it'd be worth it not > only to allow denylisting both reads and writes, but to be able to choose > from the set of reads|writes|both on a per-partition basis. > > ~Josh > > > On Thu, Aug 26,

Re: [DISCUSS] CEP-13: Denylisting partitions

g a high level view of the feature from > > what Jon and I are working on to bring to this discussion. > > > > > > On Tue, Aug 17, 2021 at 1:40 PM Sumanth Pasupuleti < > > sumanth.pasupuleti...@gmail.com> wrote: > > > >> +1 to collaborating on t

Re: [DISCUSS] CEP-13: Denylisting partitions

gt; you think? > > ~Josh > > On Mon, Aug 16, 2021 at 2:14 PM Sumanth Pasupuleti < > sumanth.pasupuleti...@gmail.com> wrote: > > > Starting a discussion thread for CEP-13 > > > > > https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-13%3A+Denyl

Re: Welcome Adam Holmberg as Cassandra committer

Congratulations Adam!! On Mon, Aug 16, 2021 at 10:32 PM Berenguer Blasi wrote: > Well done Adam, congrats! > > On 16/8/21 18:27, Andrés de la Peña wrote: > > Congrats Adam, well deserved! > > > > On Mon, 16 Aug 2021 at 17:14, Patrick McFadin > wrote: > > > >> Great to see you on the committer

[DISCUSS] CEP-13: Denylisting partitions

Starting a discussion thread for CEP-13 https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-13%3A+Denylisting+partitions This CEP proposes adding a new feature to Cassandra to be able to denylist partitions. Looking forward to any feedback/ thoughts. Thanks, Sumanth

Re: [VOTE] Release Apache Cassandra 4.0.0 (take2)

+1 (nb) Confirmed passing j8 UTs and dtests https://app.circleci.com/pipelines/github/sumanth-pasupuleti/cassandra/77/workflows/7b0ad00d-7ae3-41d2-b1a7-82fa63b7 On Wed, Jul 14, 2021 at 11:03 AM Jeremy Hanna wrote: > +1 (nb) > > > On Jul 15, 2021, at 3:42 AM, Blake Eggles

Re: [VOTE] CIP-9: Make SSLContext creation pluggable

+1 non-binding On Tue, Jul 13, 2021 at 10:05 PM Berenguer Blasi wrote: > +1 > > On 14/7/21 0:34, Nate McCall wrote: > > +1 > > > > > > On Wed, Jul 14, 2021 at 2:49 AM Benjamin Lerer > wrote: > > > >> Hi everyone, > >> > >> I am proposing the CIP-9 (Make SSLContext creation pluggable) for >

Re: Obfuscation of passwords in audit loging, in or not in 4.0?

> I am on the side of "this sounds like a really bad bug" for the audit pieces, maybe less so than FQL. Anyone using audit for real probably has meaningful audit requirements, which means they're in an industry where they get audited for security, which means logging passwords is a big deal. +1.

Re: Welcome Dinesh Joshi as Cassandra PMC member

Congratulations Dinesh!! On Wed, Jun 2, 2021 at 4:21 PM J. D. Jordan wrote: > Congrats! Well deserved addition > > > On Jun 2, 2021, at 6:10 PM, Paulo Motta > wrote: > > > > Very happy to see Dinesh as a PMC member, congratulations! > > > >> Em qua., 2 de jun. de 2021 às 17:52, Joseph Lynch <

Re: Welcome Caleb Rackliffe as Cassandra committer

Congratulations Caleb!! On Sun, May 16, 2021 at 6:29 PM Jeremy Hanna wrote: > Congratulations Caleb! > > > On May 14, 2021, at 11:02 PM, Mick Semb Wever wrote: > > > > The PMC members are pleased to announce that Caleb Rackliffe has > > accepted the invitation to become committer. > > > >

Re: Welcome Stefan Miklosovic as Cassandra committer

Congratulations Stefan!! On Mon, May 3, 2021 at 8:41 AM Brandon Williams wrote: > Congratulations, Stefan! > > On Mon, May 3, 2021 at 10:38 AM Benjamin Lerer wrote: > > > > The PMC's members are pleased to announce that Stefan Miklosovic has > > accepted the invitation to become committer

Re: [DISCUSSION] Next release roadmap

I plan to work on the following 1. CASSANDRA-12106 Blacklisting bad partitions - Rework patch and solicit for feedback/review and have it committed 2. CASSANDRA-14557

Re: [DISCUSSION] When should we branch 4.0 and unfreeze trunk?

(mostly reiterating) +1 to branching and unfreezing trunk, and to codifying the release cadence. Excited about the 4.0 rc! and looking forward to the roadmap discussion!! On Thu, Mar 25, 2021 at 8:18 AM Paulo Motta wrote: > > My thinking was talking about when to lift the freeze was moot if we

Re: Welcome Berenguer Blasi as Cassandra committer

Congratulations Berenguer!! On Thu, Mar 25, 2021 at 6:18 AM Paulo Motta wrote: > Congratulations Berenguer, well deserved! Happy to see the project > recognizing more contributors! > > Em qui., 25 de mar. de 2021 às 10:09, Brandon Williams > escreveu: > > > Congratulations Berenguer! Thank you

Re: Project Roadmap

+1 to the idea of the project roadmap and the said benefits for planning. In my opinion, it certainly does a world of good for visibility on what is in the works/ what to look forward to for both the developers as well as users. So long as "allowed work" is not restricted to items in the project

Re: New Cassandra website for review

Awesome!! On Fri, Feb 26, 2021 at 3:32 PM Benedict Elliott Smith wrote: > Very nice. > > On 26/02/2021, 21:36, "Melissa Logan" wrote: > > Hi all, > > We are excited to share the almost-complete Cassandra website design > (CASSANDRA-16115). Huge thanks to Lorina Poland, Anthony

Re: Welcome Paulo Motta as Cassandra PMC member

Congratulations Paulo! On Tue, Feb 9, 2021 at 8:10 AM Jasonstack Zhao Yang < jasonstack.z...@gmail.com> wrote: > Congrats Paulo! > > On Wed, 10 Feb 2021 at 00:03, Ekaterina Dimitrova > wrote: > > > Congrats! Well done! > > > > On Tue, 9 Feb 2021 at 11:02, J. D. Jordan > > wrote: > > > > >

Re: [DISCUSS] When to stop supporting Python 2

>From the "Supported upgrade path for 4.0" discussion, it seems like there was consensus around supporting the "3.0 -> 4.0" upgrade path as well (in addition to 3.11 -> 4.0), so we may need to add python3 support for 3.0 as well? Internally. we had a need to make 3.0 cqlsh python3 compatible, and

Re: [DISCUSS] When to stop supporting Python 2

+1 (nb) for dropping support for python2; I agree 4.0 major release is a good time to do this, given python2 is already EOL. On Mon, Jan 25, 2021 at 2:00 PM Yifan Cai wrote: > +1 nb. > We probably also want to set a milestone to get rid of the python2 > compatible code completely, if we are

Re: Welcome Yifan Cai as Cassandra committer

Congratulations Yifan! On Fri, Dec 25, 2020 at 3:45 AM Berenguer Blasi wrote: > Congrats Yifan! > > On 23/12/20 23:59, Wei Deng wrote: > > Congrats Yifan! So happy to see you taking a bigger role in the > community! > > > > -Wei > > > > On Mon, Dec 21, 2020 at 10:10 AM Benjamin Lerer < >

Re: Welcome Jordan West, David Capwell, Zhao Yang and Ekaterina Dimitrova as Cassandra committers

Hearty congratulations everyone!! On Wed, Dec 16, 2020 at 2:53 PM Joshua McKenzie wrote: > Congrats everyone! Great to see new folks joining the project. > > On Wed, Dec 16, 2020 at 3:55 PM Dinesh Joshi wrote: > > > Congratulations everyone! > > > > Dinesh > > > > > On Dec 16, 2020, at 8:55

Re: [DISCUSS] Bringing protocol v5 out of beta and dropping support from 3.11.x

+1 to moving v5-beta changes in trunk to new protocol v6. Regarding 3.11 and v5, I suppose we could say, v5 could never get matured beyond beta, but not sure if it would be confusing to see v6 while v5 is still in beta (curious on others' thoughts as well) On Tue, Dec 8, 2020 at 12:33 PM Mick

Re: [DISCUSS] CASSANDRA-12126: LWTs correcteness and performance

Knowing there is a correctness issue in LWT, and given users use LWT primarily for correctness, my opinion is we should commit the correctness patch (makes it one of #1, #3 or #4) I agree we should not cause further delay to 4.0 release (making it one of #3 or #4). Con for #3 would be,

Re: [VOTE] Release Apache Cassandra 3.11.9

Verified unit tests and dtests https://app.circleci.com/pipelines/github/sumanth-pasupuleti/cassandra?branch=3119_tentative 1 Unit test fails (testIndexMemtableSwitching - org.apache.cassandra.index.sasi.SASIIndexTest), it succeeds on local isolated execution though. 1 dtest failure

Re: [VOTE] Release Apache Cassandra 3.0.23

Verified Unit tests and DTests. https://app.circleci.com/pipelines/github/sumanth-pasupuleti/cassandra?branch=3023_tentative One dtest fails (test_closing_connections - thrift_hsha_test.TestThriftHSHA). +1 (non binding) On Thu, Oct 29, 2020 at 5:36 AM Mick Semb Wever wrote: > Propos

Re: [VOTE] Release Apache Cassandra 4.0-beta3

Verified unit tests and dtests https://app.circleci.com/pipelines/github/sumanth-pasupuleti/cassandra?branch=40_beta3_tentative Observed a dtest failure that seems flaky test_insert_data_during_replace_same_address - replace_address_test.TestReplaceAddress java.lang.IllegalStateException: Unable

Re: Supported upgrade path for 4.0

+1 to officially supporting 3.0 to 4.0, in addition to 3.11 to 4.0 upgrade paths On Thu, Oct 8, 2020 at 10:33 PM Jeff Jirsa wrote: > > I assumed it would be 3.0.x and 3.11.x > > I don’t know why we’d make 3.0-4.0 unofficial/unsupported - there’s no > technical reason I’ve seen > > > On Oct 8,

Re: [VOTE] Accept the Harry donation

+1 (non-binding) On Wed, Sep 16, 2020 at 7:41 AM Jon Meredith wrote: > +1 (non-binding) > > On Wed, Sep 16, 2020 at 8:28 AM David Capwell > wrote: > > > > +1 > > > > Sent from my iPhone > > > > > On Sep 16, 2020, at 6:34 AM, Brandon Williams > wrote: > > > > > > +1 > > > > > >> On Wed, Sep

Re: [DISCUSS] CEP-8 Drivers Donation

This is great! +1 to the phased approach mentioned in the document of starting with the Java driver, and then including the learnings if any into the rest of the drivers' donation. Also excited about the documentation donation - it will be nice to not have to depend on the mentioned proprietary

Re: [VOTE] Release Apache Cassandra 3.11.7

Ran following circleCI tests j8_unit_tests (1 failing) - testIndexMemtableSwitching - org.apache.cassandra.index.sasi.SASIIndexTest with exception junit.framework.AssertionFailedError: expected:<0> but was:<1>, at

Re: [VOTE] Release Apache Cassandra 3.0.21

Ran following circleCI tests j8_unit_tests (PASS) j8_jvm_dtests (PASS) j8_dtests (5 failures, in each of with vnodes, and no-vnodes) On Tue, Jul 14, 2020 at 3:50 PM Mick Semb Wever wrote: > Proposing the test build of Cassandra 3.0.21 for release. > > sha1:

Re: [VOTE] Release Apache Cassandra 2.2.17

Ran following CircleCI tests j8_unit_tests (PASS) j8_jvm_dtests (1 failure "namedDcTest - org.apache.cassandra.distributed.test.NetworkTopologyTest" with "java.util.concurrent.TimeoutException") j8_dtests (60 failures in no-vnodes (all of them are from cqlsh_tests/test_cqlsh.py), 62 failures in

Re: [VOTE] Release Apache Cassandra 4.0-beta1

+1 nb Ran following CircleCI tests j8_unit_tests (PASS) j8_jvm_dtests (PASS) j8_dtests (PASS) On Thu, Jul 16, 2020 at 10:18 AM Jordan West wrote: > +1 nb > > On Thu, Jul 16, 2020 at 9:38 AM Yifan Cai wrote: > > > +1 nb > > > > > > From: Robert Stupp > > Sent:

Re: [DISCUSS] Revisiting Java 11's experimental status

We at Netflix have been testing 4.0 on Java 8, and we do not plan to use Java 11 yet for C*, since we are, and for the considerable future will be running Java 8 only in production. On Mon, Jul 13, 2020 at 2:41 PM Patrick McFadin wrote: > JDK8 seems like the safe devil we know, but in the

Re: Scope of CASSANDRA-14557 (Default and Minimum RF)

d probably add is a line in cassandra.conf that default and min > replication factors will also apply to system keyspaces. > > On Wed, May 13, 2020 at 9:01 PM Sumanth Pasupuleti < > sumanth.pasupuleti...@gmail.com> wrote: > > > Hi, > > > > Based on

Scope of CASSANDRA-14557 (Default and Minimum RF)

Hi, Based on Alex's suggestion on the ticket, wanted to reach out to clarify on the current scope of default and minimum replication factors that 14557 defines, and gather thoughts to farm for dissent. Both the configurations (default and minimum) apply not just to user keyspaces, but also to

Re: Discussion: addition to CEP guide

+1 (nb) On Fri, Apr 24, 2020 at 8:01 PM Dinesh Joshi wrote: > +1 > > > On Apr 24, 2020, at 5:37 PM, Joshua McKenzie > wrote: > > > > Updated. Thanks for the feedback. > > > > On Fri, Apr 24, 2020 at 8:08 PM sankalp kohli > > wrote: > > > >> +1 > >> > >> On Thu, Apr 23, 2020 at 6:07 AM Andrés

Re: [VOTE] Release Apache Cassandra 2.2.16

+1 non-binding All UTs and Dtests pass except for two (thrift_hsha_test.TestThriftHSHA, bootstrap_test.TestBootstrap) https://circleci.com/workflow-run/f4e396c5-36f8-4db4-ac8c-6f0578f217a0 On Thu, Feb 13, 2020 at 2:16 AM Mick Semb Wever wrote: > > > The vote will be open for 72 hours (longer

Re: [VOTE] Release Apache Cassandra 3.11.6

+1 non-binding All UTs and Dtests pass except for two (thrift_hsha_test.TestThriftHSHA, bootstrap_test.TestBootstrap) https://circleci.com/workflow-run/6fa3a0ac-98c9-40d9-be07-058b80b99738

Re: [VOTE] Release Apache Cassandra 4.0-alpha3

Java8 Test run summary for 4.0-alpha3-tentative Passing UTs: https://circleci.com/gh/sumanth-pasupuleti/cassandra/852 Passing jvm_dtests: https://circleci.com/gh/sumanth-pasupuleti/cassandra/853 1 failing dtest ( https://circleci.com/gh/sumanth-pasupuleti/cassandra/855#tests/containers/92 , https

Re: [VOTE] Cassandra Enhancement Proposal (CEP) documentation

+1 On Fri, Nov 1, 2019 at 2:55 PM Joseph Lynch wrote: > +1 > > -Joey > > On Fri, Nov 1, 2019 at 5:33 AM Mick Semb Wever wrote: > > > Please vote on accepting the Cassandra Enhancement Proposal (CEP) > document > > as a starting point and guide towards improving collaboration on, and > >

Re: [VOTE] Release Apache Cassandra 3.11.5

CircleCi test runs ( https://circleci.com/workflow-run/92c41011-b4d1-4dc5-9d21-8fbb2950a5f1): j8_unit_tests: Pass j8_jvm_dtests: Pass j8_dtests-no-vnodes: 1 failure (test_closing_connections - thrift_hsha_test.TestThriftHSHA) j8_dtests-no-vnodes: 1 failure (test_closing_connections -

Re: [VOTE] Release Apache Cassandra 3.0.19

CircleCi test runs ( https://circleci.com/workflow-run/b8abe6cf-1584-4937-958c-0dc1280e2f3a): j8_unit_tests: Pass j8_jvm_dtests: Pass j8_dtests-no-vnodes: 1 failures (test_closing_connections - thrift_hsha_test.TestThriftHSHA) j8_dtests-no-vnodes: 1 failures (test_closing_connections -

Re: [VOTE] Release Apache Cassandra 2.2.15

CircleCi test runs ( https://circleci.com/workflow-run/2ca1a202-7505-431d-87d3-c0f93b14bddd): j8_unit_tests: Pass j8_jvm_dtests: Pass j8_dtests-no-vnodes: 3 failures (test_short_read_delete - consistency_test.TestConsistency, test_simple_rebuild - rebuild_test.TestRebuild, test_closing_connections

Re: Can we kick off a release?

Looks like https://issues.apache.org/jira/browse/CASSANDRA-15363 is in "Ready to Commit" state. Can we have this committed, before cutting the next set of releases? Thanks, Sumanth On Wed, Oct 23, 2019 at 8:13 AM Blake Eggleston wrote: > Looks like 15193 has been committed. Are we waiting on

Re: [VOTE] Apache Cassandra Release Lifecycle

Thank you, Scott! I've moved the document content (along with outstanding comments) into cwiki at https://cwiki.apache.org/confluence/display/CASSANDRA/Release+Lifecycle. Made the GDoc deprecated and view-only, and left breadcrumbs to the cwiki in both the jira

Re: [VOTE] Apache Cassandra Release Lifecycle

t; history. Otherwise it's not entirely clear what was voted on. > >> > >> > >> On 30/09/2019, 20:10, "Sumanth Pasupuleti" < > >> sumanth.pasupuleti...@gmail.com> wrote: > >> > >>+1 > >> > >>On Mon, Sep 30

Re: [VOTE] Apache Cassandra Release Lifecycle

+1 On Mon, Sep 30, 2019 at 12:00 PM Nate McCall wrote: > +1 > > On Tue, Oct 1, 2019 at 7:52 AM sankalp kohli > wrote: > > > Hi, > > We have discussed in the email thread[1] about Apache Cassandra > Release > > Lifecycle. We came up with a doc[2] for it. Please vote on it if you > agree > >

Re: 4.0 Max TTL

We will have to deal with fixing this TTL issue eventually as more users start to deal with the boundaries of currently allowed TTL (which keeps declining). It will be neat if we can get this into 4.0 before it is released - be it in beta or future 4.0 alpha(s) - the sooner the better, as everyone

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

One more call for any additional comments/ feedback on the release lifecycle document https://docs.google.com/document/d/1bS6sr-HSrHFjZb0welife6Qx7u3ZDgRiAoENMLYlfz8/edit# Thanks, Sumanth On Sat, Jul 27, 2019 at 1:01 AM Sumanth Pasupuleti < sumanth.pasupuleti...@gmail.com> wrote: >

Re: [VOTE] Release Apache Cassandra 4.0-alpha1 (24 hour vote)

I have started running fuzz tests ( https://github.com/Netflix/ndbench/wiki/Fuzz-Testing), will update in case of any interesting findings. Thanks, Sumanth On Fri, Sep 6, 2019 at 4:01 AM Benedict Elliott Smith wrote: > I think anybody can run these tests locally. It's just possible to pay to

Re: Contributing cassandra-diff

No hard preference on the repo, but just excited about this tool! Looking forward to employing this for upgrade testing (very timely :)) On Thu, Aug 22, 2019 at 3:38 AM Sam Tunnicliffe wrote: > My own weak preference would be for a dedicated repo in the first > instance. If/when additional

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

CASSANDRA-13951 > [3] https://issues.apache.org/jira/browse/CASSANDRA-13994 > > > > On Sat, Jun 22, 2019 at 1:25 AM Sumanth Pasupuleti < > sumanth.pasupuleti...@gmail.com> wrote: > > > Thanks for the feedback Scott. I have incorporated all the incremental > > feedback

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

lt JVM settings would be nice, > for > > >>>> example. Improving documentation (the data modeling section in > > >>>> particular), fixing the dynamic snitch issues [1], and some > > improvements > >

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

modeling section in > >>>> particular), fixing the dynamic snitch issues [1], and some > improvements > >>> to > >>>> virtual tables like exposing the sstable metadata [2], and exposing > table > >>>> statistics [3] come

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

355 > >> > >> > >> On 2019. 05. 23. 19:30, ajs6f wrote: > >>> +1 in the fullest degree. A date that needs to be changed is still > >> enormously more attractive than no date at all. > >>> > >>> Adam Soroka > >>> > &g

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

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 at 8:52 AM Dinesh Joshi wrote: > +1 on setting a date. > > Dinesh > > > On May 23, 2019, at 11:07 AM, Michael Shuler > wrote: > > > > We've had 4.0 listed as TBD

Re: CASSANDRA-14482

+1 On Fri, Feb 15, 2019 at 12:14 PM Dikang Gu wrote: > +1 > > On Fri, Feb 15, 2019 at 10:27 AM Vinay Chella > wrote: > > > We have been using Zstd compressor across different products/services > here > > and have seen significant improvements, getting this in 4.0 would be a > big > > win. > >

Re: Request to review feature-freeze proposed tickets

ould honor it (more in the JIRA). Thanks, Sumanth On Tue, Jan 15, 2019 at 8:46 AM Sumanth Pasupuleti < sumanth.pasupuleti...@gmail.com> wrote: > With 14303 in (thanks to Jon), wanted to see if I can get help on 14557 - > it makes it further easy to create keyspaces (without having

Re: Request to review feature-freeze proposed tickets

With 14303 in (thanks to Jon), wanted to see if I can get help on 14557 - it makes it further easy to create keyspaces (without having to always mention RF) and provides a way to ensure keyspaces are created with a minimum required RF. Thanks, Sumanth On Wed, Dec 5, 2018 at 5:35 PM Vinay Chella

Feedback request for Message Flusher bug found in 3.0.17

Hi, We recently found this issue on one of our 3.0.17 clusters, where the Message Flusher falls off the event loop, eventually resulting in OOM on a bunch of nodes. We saw this happen twice so far. CASSANDRA-14855 has all the details

Feedback request for Message Flusher bug found in 3.0.17 (CASSANDRA-14855)

Hi, We recently found this issue on one of our 3.0.17 clusters, where the Message Flusher falls off the event loop, eventually resulting in OOM on a bunch of nodes. We saw this happen twice so far. CASSANDRA-14855 has all the details

Re: Proposed changes to CircleCI testing workflow

Hi Stefan, +1 on the CircleCI changes. A few months ago, I took a shot at CircleCI to add support for Java 1.7 and in the process (perhaps the more important takeaway), explored adding "aliases" to avoid code duplication in the yml file (

Re: [VOTE] Accept GoCQL driver donation and begin incubation process

+1 On Wed, Sep 12, 2018 at 10:37 AM Dinesh Joshi wrote: > +1 > > Dinesh > > > On Sep 12, 2018, at 10:23 AM, Jaydeep Chovatia < > chovatia.jayd...@gmail.com> wrote: > > > > +1 > > > > On Wed, Sep 12, 2018 at 10:00 AM Roopa Tangirala > > wrote: > > > >> +1 > >> > >> > >> *Regards,* > >> > >>

Re: [VOTE] Development Approach for Apache Cassandra Management process

Option "b". Thanks, Sumanth On Wed, Sep 12, 2018 at 9:59 AM Roopa Tangirala wrote: > +1 to b Take the best from existing side cars and make a great side car > which ships with cassandra > > > *Regards,* > > *Roopa Tangirala* > > Engineering Manager CDE > > *(408) 438-3156 - mobile* > > > > > >

Re: Supporting multiple JDKs

quot; support for that Java > version. Nice to have at this point, as there will be plenty of bugs in > 4.0 to fix, until we should spend time looking more closely for more > subtle Java 11 issues. But if someone wants to contribute any work to > make this happen, I'd be glad to have that opt

Re: Supporting multiple JDKs

> And I would suggest to go further and crash the build with JDK1.7 so we can take away the possibility for users to shoot their foot off this way. I like this suggestion. Either we should be on the side of NO support to JDK 1.7, or if we say we support JDK1.7, I believe we should be building

Re: Supporting multiple JDKs

C* 2.2 > I'm still left wondering why we want to use CI resources to find bugs that the users will never encounter. How would we be sure users will never encounter bugs unless we build against that JDK? This is the reason I propose having a CircleCI build against 1.7. > If you take out "and

Re: upgrade guava on trunk before 9/1?

with the Github branch and CircleCI details. Thanks, Sumanth On Fri, Aug 17, 2018 at 2:32 PM Sumanth Pasupuleti wrote: > Thanks for the confirmation Andy. > > Created a JIRA to track the guava upgrade > https://issues.apache.org/jira/browse/CASSANDRA-14655. > > I current put t

Re: [Discuss] Accept GoCQL driver donation

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: Reaper as cassandra-admin

IMO, I am glad to see there are at least three solutions here to address repair and can be potential candidates for sidecar. As Joey pointed out, all of them may not be great at everything they do, and to me, it makes sense to "cherry pick" the best each product has, and build a good C* sidecar.

Re: Supporting multiple JDKs

far If anyone has any further feedback, please comment. Thanks, Sumanth On Fri, Aug 24, 2018 at 7:27 AM Sumanth Pasupuleti wrote: > > I'm still a bit confused as to what's the benefit in compiling with > jdk1.7 and then testing with jdk1.7 or jdk1.8 > I meant two separate workflows

Re: Supporting multiple JDKs

> I'm still a bit confused as to what's the benefit in compiling with jdk1.7 and then testing with jdk1.7 or jdk1.8 I meant two separate workflows for each JDK i.e. Workflow1: Build against jdk1.7, and optionally run UTs and Dtests against 1.7 Workflow2: Build against jdk1.8, and run UTs and

Re: Supporting multiple JDKs

I am not against using a compile-time quick-feedback tool like Animal Sniffer either. It is great to have such a tool to know of any obvious bad changes right away during development. However, in addition to using such a tool, I believe, when we make a release, we should build against the actual

Supporting multiple JDKs

Hi, The goal of this email is to arrive at a solution (probably resulting in a few follow-ups) to ensure support for multiple JDKs for different versions of Cassandra. This comes out of Jason's comment in https://issues.apache.org/jira/browse/CASSANDRA-14563. Below is the proposal. Please

Re: upgrade guava on trunk before 9/1?

stax-oss.atlassian.net/browse/JAVA-1928>) that > addresses this that will be in version 3.6.0 which should be released in > the coming weeks. After that the driver will work with Guava 16.0.1 > through 26 (We've run our full test suite against all versions in that > range). > > Thanks, &g

Re: upgrade guava on trunk before 9/1?

; resolved build issues; about 63 Unit Tests fail - a lot of them due to a NPE and another bunch due to the driver using a method that does not exist in latest Guava. Github Branch: https://github.com/sumanth-pasupuleti/cassandra/tree/guava_26_trunk Failing Unit Tests: https://circleci.com/gh/sumanth

Re: [VOTE] Branching Change for 4.0 Freeze

+1 nb On Fri, Jul 13, 2018 at 6:58 PM Jaydeep Chovatia wrote: > +1 > > On Wed, Jul 11, 2018 at 2:46 PM 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 merges into trunk. > > > >

Re: Coordinator Write Metrics per CF

ns. I can't off the top > of > > my head think of a good reason to consult this metric, that couldn't > better > > be answered elsewhere. > > > > > > > > On 13 February 2018 at 19:18, Sumanth Pasupuleti < > spasupul...@netflix.com. > > in

Re: Coordinator Write Metrics per CF

a helpful metric to > > diagnose internode networking issues - although I'll note that the read > > metric will also achieve this assuming you have enough reads to get some > > useful information out of it. > > > > On 9 February 2018 at 17:43, Sumanth Pasupuleti < > >

Coordinator Write Metrics per CF

There is an existing CoordinatorReadLatency table metric. I am looking to add CoordinatorWriteLatency table metric - however, before I attempt a shot at it, would like to know if anyone has context around why we currently do not have such metric (while we have the read metric) - if someone has

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

My final try on pushing the attachment over. ​ On Wed, Aug 9, 2017 at 4:01 PM, Sumanth Pasupuleti < sumanth.pasupuleti...@gmail.com> wrote: > Thanks for the insights Jeff! I did go through the tickets around dropping > expired sstables that have overlaps - based on what I understa

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

t; expired, and manually remove them (/bin/rm) before starting cassandra > again. It works reasonably well IF (and only if) you write all data with > TTLs, and you can identify fully expired sstables based on maximum > timestamps. > > > > > On Tue, Aug 8, 2017 at 8:51 PM, Su

TWCS High Disk Space Usage Troubleshooting - Looking for suggestions

> > Hi, > > We use TWCS in a few of the column families that have TTL based > time-series data, and no explicit deletes are issued. Over the time, we > observed the disk usage has been increasing beyond the expected levels. > > Data directory in a particular node shows SSTables that are more than