incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Will Oberman <ober...@civicscience.com>
Subject Re: 99.999% uptime - Operations Best Practices?
Date Wed, 22 Jun 2011 22:20:07 GMT
Sadly, they all went down within minutes of each other.

Sent from my iPhone

On Jun 22, 2011, at 6:16 PM, Sasha Dolgy <sdolgy@gmail.com> wrote:

> Implement monitoring and be proactive...that will stop you waking up  
> to a big surprise.  i'm sure there were symltoms leading up to all 4  
> nodes going down.  willing to wager that each node went down at  
> different times and not all went down at once...
>
> On Jun 22, 2011 11:50 PM, "Les Hazlewood" <les@katasoft.com> wrote:
> > I understand that every environment is different and it always  
> 'depends' :)
> > But recommending settings and techniques based on an existing real
> > production environment (like the user's suggestion to run nodetool  
> repair as
> > a regular cron job) is always a better starting point for a new  
> Cassandra
> > evaluator than having to start from scratch.
> >
> > Ryan, do you have any 'seed' settings that you guys use for nodes at
> > Twitter?
> >
> > Are there any resources/write-ups beyond the two I've listed  
> already that
> > address some of these 'gotchas'? If those two links are in fact  
> the ideal
> > starting point, that's fine - but it appears that this may not be  
> the case
> > however based on the aforementioned user as well as the other who  
> helped him
> > who saw similar warning signs.
> >
> > I'm hoping for someone to dispel these reports based on what  
> people actually
> > do in production today. Any info/settings/recommendations based on  
> real
> > production environments would be appreciated!
> >
> > Thanks again,
> >
> > Les

Mime
View raw message