incubator-accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Vines <john.w.vi...@ugov.gov>
Subject Re: Suspension
Date Wed, 15 Feb 2012 20:06:44 GMT
Perhaps we want a suspend option which provides the ZK timeouts one large
skew before it expects normal behavior again?

John

On Wed, Feb 15, 2012 at 12:20 PM, Aaron Cordova <aaron@cordovas.org> wrote:

> Yeah, we don't want to let designing a restart service distract us from
> the suspension discussion.
>
> Issuing a 'suspend' command sounds like a third option.
>
> So far we have:
>
> 1) run Accumulo in a mode that ignores long timeouts (perhaps enabled just
> before suspension)
> 2) let Accumulo die (no modification to Accumulo) and rely on a
> to-be-created restart service
> 3) issue a command to suspend processes before suspending the VM / OS
>
> Perhaps the 'suspend' command just enables ignorance of timeouts, but if
> you're gonna issue a command, you might as well just issue the 'shutdown'
> command.
>
> What's the start-up time like for large clusters now days?
>
> Also, what is the effect of taking all tables offline?
>
> On Feb 15, 2012, at 12:12 PM, David Medinets wrote:
>
> > It seems like the conversation has wandered away from the main point -
> > marking a node as suspended instead of having a monitoring service
> > discover that it is non-responsive. Would it possible to issue a
> > command-line 'suspend' command. And then a 'resume' command  when the
> > user is ready to have the node back in the cluster?
>
>

Mime
View raw message