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
+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
+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
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,
.
*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
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
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
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
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
