Re: [EXTERNAL] Re: [Discuss] Generic Purpose Rate Limiter in Cassandra

thread that is not captured in the CEP-41. Jaydeep On Thu, Feb 22, 2024 at 11:36 AM Jaydeep Chovatia < chovatia.jayd...@gmail.com> wrote: > Thanks, Josh. I will file an official CEP with all the details in a few > days and update this thread with that CEP number. > Thanks a lot everyone for provid

Re: [Discuss] Repair inside C*

tation details, so that feels like CEP time to me. > > If you were willing and able to get a CEP together for automated repair > based on the above material, given you've done the work and have the proof > points it's working at scale, I think this would be a *huge contribution* > to

Re: [EXTERNAL] Re: [Discuss] Generic Purpose Rate Limiter in Cassandra

ake it there? > > +1 here. > > Synthesizing your gdoc, Caleb's work, and the feedback from this thread > into a draft seems like a solid next step. > > On Wed, Feb 7, 2024, at 12:31 PM, Jaydeep Chovatia wrote: > > I see a lot of great ideas being discussed or proposed i

Re: [EXTERNAL] Re: [Discuss] Generic Purpose Rate Limiter in Cassandra

I see a lot of great ideas being discussed or proposed in the past to cover the most common rate limiter candidate use cases. Do folks think we should file an official CEP and take it there? Jaydeep On Fri, Feb 2, 2024 at 8:30 AM Caleb Rackliffe wrote: > I just remembered the other day that I

Re: [EXTERNAL] Re: [Discuss] Generic Purpose Rate Limiter in Cassandra

s in order for this to work optimally, b/c you might not want to wait >> for query timeouts before you throttle. I think there's a lot of value in >> dynamically adaptive compaction, repair, and streaming since it would >> prioritize user requests, but again, if you're not willing

Re: [EXTERNAL] Re: [Discuss] Generic Purpose Rate Limiter in Cassandra

imilar things > internally  > > Thanks, > German > ------ > *From:* Jaydeep Chovatia > *Sent:* Tuesday, January 16, 2024 1:16 PM > *To:* dev@cassandra.apache.org > *Subject:* [EXTERNAL] Re: [Discuss] Generic Purpose Rate Limiter in > Cassandra >

Re: [Discuss] Generic Purpose Rate Limiter in Cassandra

ible that Java driver > would start to see this node as "erroneous" with delayed response time etc > and it would start to prefer other nodes in the cluster when deciding what > node to contact for query coordination? So you would put more load on other > nodes, making them mo

[Discuss] Generic Purpose Rate Limiter in Cassandra

Hi, Happy New Year! I would like to discuss the following idea: Open-source Cassandra (CASSANDRA-15013 ) has an elementary built-in memory rate limiter based on the incoming payload from user requests. This rate limiter activates if any

Re: Need Confluent "Create" permission for filing a CEP

Thank you! On Tue, Oct 10, 2023 at 2:58 AM Brandon Williams wrote: > I've added you, you should have access now. > > Kind Regards, > Brandon > > On Tue, Oct 10, 2023 at 1:24 AM Jaydeep Chovatia > wrote: > > > > Hi, > > > > I want to create a new

Need Confluent "Create" permission for filing a CEP

Hi, I want to create a new CEP request but do not see the "Create" page permission on Confluent . Could someone permit me? Here is the CEP draft: [DRAFT] CEP - Apache Cassandra Official Repair Solution - Google Docs

Re: [Discuss] Repair inside C*

Is anyone going to file an official CEP for this? As mentioned in this email thread, here is one of the solution's design doc and source code on a private Apache Cassandra patch. Could you

[Discuss] Detecting token-ownership mismatch

Hi, As we know, Cassandra exchanges important topology and token-ownership-related details over Gossip. Cassandra internally maintains the following two separate caches that have the token-ownership information maintained: 1) Gossip cache and 2) Storage Service cache. The first Gossip cache is

Re: [Discuss] Repair inside C*

ide C* > > As someone who has done a lot of work trying to make repair stable, I > approve of this message ^_^ > > More than glad to help mentor this work > > On Jul 24, 2023, at 6:29 PM, Jaydeep Chovatia > wrote: > > To clarify the repair solution timing, the one we h

Re: [Discuss] Repair inside C*

time about having repairs in the Open Source Cassandra itself. As mentioned in my previous email, any solution getting adopted is fine; the important aspect is to have a repair solution in the OSS Cassandra itself! Yours Faithfully, Jaydeep On Mon, Jul 24, 2023 at 3:46 PM Jaydeep Chovatia wrote

Re: [Discuss] Repair inside C*

Hi German, The goal is always to backport our learnings back to the community. For example, I have already successfully backported the following two enhancements/bug fixes back to the Open Source Cassandra, which are described in the article. I am already currently working on open-source a few

Cassandra 3.0.27 - Tombstone disappeared during node replacement

Hi, I am running Cassandra 3.0.27 in my production. In some corner case scenarios, we have tombstones disappearing during bootstrap/decommission. I've outlined a possible theory with the root cause in this ticket: https://issues.apache.org/jira/browse/CASSANDRA-17991 Could someone please help

Re: Cassandra Token ownership split-brain (3.0.14)

lp triage a bug report against a current release of > the database. > > - Scott > > On Sep 6, 2022, at 5:13 PM, Jaydeep Chovatia > wrote: > >  > If anyone has seen this issue and knows a fix, it would be a great help! > Thanks in advance. > > Jaydeep > > On F

Re: Cassandra Token ownership split-brain (3.0.14)

If anyone has seen this issue and knows a fix, it would be a great help! Thanks in advance. Jaydeep On Fri, Sep 2, 2022 at 1:56 PM Jaydeep Chovatia wrote: > Hi, > > We are running a production Cassandra version (3.0.14) with 256 tokens > v-node configuration. Occasion

Cassandra Token ownership split-brain (3.0.14)

Hi, We are running a production Cassandra version (3.0.14) with 256 tokens v-node configuration. Occasionally, we see that different nodes show different ownership for the same key. Only a node restart corrects; otherwise, it continues to behave in a split-brain. Say, for example, *NodeA*

Cassandra 3.0 - A new node is not able to join the cluster

Hi, I've a production Cassandra cluster from 3.0.14 branch. Each node consists of roughly 1.5TB data with a ring size 70+70. I need to add more capacity to meet production demand, but when I add 71st node, then it streams data from other nodes as expected, but after some-time it spends an

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

+1 On Wed, Sep 12, 2018 at 10:00 AM Roopa Tangirala wrote: > +1 > > > *Regards,* > > *Roopa Tangirala* > > Engineering Manager CDE > > *(408) 438-3156 - mobile* > > > > > > > On Wed, Sep 12, 2018 at 8:51 AM Sylvain Lebresne > wrote: > > > -0 > > > > The project seems to have a hard time

Re: [VOTE] Branching Change for 4.0 Freeze

+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. > > a. Bug and Perf fixes to 4.0. > b. Critical bugs in any version of C*. > c. Testing

Re: Real time bad query logging framework in C*

uld allow to expose internal events to external processes that > would be able to analyze these events, alert users, or event act on > them. It's a different approach from what you're suggesting, but just > wanted to mention this and maybe you'd agree that having external > processes f

Real time bad query logging framework in C*

Hi, We have worked on developing some common framework to detect/log anti-patterns/bad queries in Cassandra. Target for this effort would be to reduce burden on ops to handle Cassandra at large scale, as well as help beginners to quickly identify performance problems with the Cassandra. Initially

Re: Proposing an Apache Cassandra Management process

In my opinion this will be a great addition to the Cassandra and will take overall Cassandra project to next level. This will also improve user experience especially for new users. Jaydeep On Thu, Apr 12, 2018 at 2:42 PM Dinesh Joshi wrote: > Hey all - > With

Re: Flakey Dtests

ed.. > Hope this answers your question! There are quite a few dtests currently > failing and as Jeff mentioned I’ve created JIRAs for a lot of them already > so any help (no matter how trivial or annoying it might be or seem) to get > everything green again. > > best, > kjellman

Re: Flakey Dtests

Is there a way to check which tests are failing in trunk currently? Previously this URL was giving such results but is no longer working. Jaydeep On Wed, Nov 15, 2017 at 5:44 PM, Jeff Jirsa wrote: > In lieu of a weekly wrap-up, here's a