Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Accumulo >> mail # user >> Suspension


Copy link to this message
-
Re: Suspension
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?