incubator-accumulo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aaron Cordova <>
Subject Re: Suspension
Date Wed, 15 Feb 2012 15:38:41 GMT
Such an option would have to be very conspicuous so that users don't accidentally enable it
and then wonder why bad tablet servers aren't removed automatically from the cluster.

It would also require some thought to make sure that large gaps in all processes' consciousnesses
(5 s's in that word!) don't cause other undesirable effects.

On Feb 15, 2012, at 10:31 AM, John Vines wrote:

> That sounds to hacky. Why not just have a Config option for whether zk timeouts are heeded?
> On Feb 15, 2012 10:26 AM, "Adam Fuchs" <> wrote:
> I think this makes a lot of sense. I use Accumulo enough on a laptop to be annoyed at
how often I have to run
> One way we could do this is to have a separate daemon process restart accumulo processes
anytime they go down. I think log recovery is almost as efficient as any other way of suspending
memory to disk, and it doesn't add any extra complexity to the code base. The only other concern
is having the daemon restart a process that should actually be down, and we would have to
work out the model for that.
> Adam
> On Wed, Feb 15, 2012 at 9:54 AM, Aaron Cordova <> wrote:
> EC2 as well as laptop users would be interested in making Accumulo 'suspendable'. The
self-monitoring features end up killing off processes upon awakening. Perhaps this could be
implemented by a simple switch that tells Accumulo not to worry about abandoning processes
that don't report, that can be enabled before suspension and disabled after .. or simply left
enabled for stand-alone laptop users.
> Does it make sense to make it possible to suspend a running Accumulo instance, or should
this simply be discouraged and made well known?

View raw message