Re: Contributing cassandra-diff

Markus, This is great and very helpful for anyone running Cassandra in production and have peace of mind to roll out upgrades. Thank you ! *Director, Cloud Data Engineering* *Regards,Roopa Tangirala* On Thu, Aug 22, 2019 at 9:14 AM Michael Shuler wrote: > CI git polling for changes o

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

+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 getting on top of reviewing his > backlog > of 'patch available' issu

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

+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* On Wed, Sep 12, 2018 at 8:19 AM sankalp kohli wrote: > Hi, > Community has been discussing about

Re: Reaper as cassandra-admin

e confines of the decisions that were already made. Practically speaking once a codebase is established there is inertia in making architectural changes and we're left dealing with technical debt. *Regards,* *Roopa Tangirala* Engineering Manager CDE *(408) 438-3156 - mobile* On Mon,

Re: Yet another repair solution

+1 interested in seeing and understanding another repair solution. > On Aug 28, 2018, at 1:03 PM, Joseph Lynch wrote: > > I'm pretty interested in seeing and understanding your solution! When we > started on CASSANDRA-14346 reading your design documents and plan you > sketched out in CASSANDRA-

Re: Proposing an Apache Cassandra Management process

. *Regards,* *Roopa Tangirala* Engineering Manager CDE *(408) 438-3156 - mobile* On Mon, Aug 20, 2018 at 2:58 PM Joseph Lynch wrote: > > We are looking to contribute Reaper to the Cassandra project. > > > Just to clarify are you proposing contributing Reaper as a project via &g

Re: Proposing an Apache Cassandra Management process

maintenance fixes easily. Thanks Roopa > On Aug 17, 2018, at 8:52 AM, Blake Eggleston wrote: > > I'd be more in favor of making it a separate project, basically for all the > reasons listed below. I'm assuming we'd want a management process to work > across dif

Re: [VOTE] Branching Change for 4.0 Freeze

+ 1 Thanks, Roopa Tangirala > On Jul 13, 2018, at 1:38 PM, Nate McCall wrote: > > +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, san

Re: Testing 4.0 Post-Freeze

ements, streaming and share the results. *Regards,* *Roopa Tangirala* Engineering Manager CDE *(408) 438-3156 - mobile* On Tue, Jul 3, 2018 at 2:32 PM dinesh.jo...@yahoo.com.INVALID wrote: > I think the call to action for the community here is to focus efforts on > testing and bu

Re: Repair scheduling tools

others can fall back to default repairs. *Regards,* *Roopa Tangirala* Engineering Manager CDE *(408) 438-3156 - mobile* On Tue, Apr 3, 2018 at 4:19 PM, Kenneth Brotman < kenbrot...@yahoo.com.invalid> wrote: > Why not make it configurable? > auto_manage_repair_consi

Re: New committers announcement

Congratulations to all the new committers! *Regards,* *Roopa Tangirala* Engineering Manager CDE *(408) 438-3156 - mobile* On Wed, Feb 15, 2017 at 7:48 AM, Edward Capriolo wrote: > Three cheers! > Hip , Hip, NotFound > 1 ms later > Hip, Hip, Hooray > 1 ms later > Hoor

Re: Dropped messages on random nodes.

Dikang, Did you take a look at the heap health on those nodes? A quick heap histogram or dump would help you figure out if it is related to data issue(wide rows, or bad model) where few nodes may be coming under heap pressure and dropping messages. Thanks, Roopa *Regards,* *Roopa Tangirala