Return-Path: X-Original-To: apmail-incubator-accumulo-user-archive@minotaur.apache.org Delivered-To: apmail-incubator-accumulo-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7D97E9635 for ; Wed, 15 Feb 2012 15:39:39 +0000 (UTC) Received: (qmail 36026 invoked by uid 500); 15 Feb 2012 15:39:39 -0000 Delivered-To: apmail-incubator-accumulo-user-archive@incubator.apache.org Received: (qmail 36008 invoked by uid 500); 15 Feb 2012 15:39:39 -0000 Mailing-List: contact accumulo-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: accumulo-user@incubator.apache.org Delivered-To: mailing list accumulo-user@incubator.apache.org Received: (qmail 35999 invoked by uid 99); 15 Feb 2012 15:39:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2012 15:39:39 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.216.54] (HELO mail-qw0-f54.google.com) (209.85.216.54) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Feb 2012 15:39:34 +0000 Received: by qaea17 with SMTP id a17so1350511qae.6 for ; Wed, 15 Feb 2012 07:39:13 -0800 (PST) Received: by 10.229.78.87 with SMTP id j23mr15629173qck.87.1329320324319; Wed, 15 Feb 2012 07:38:44 -0800 (PST) Received: from new-host.home (pool-71-246-213-152.washdc.fios.verizon.net. [71.246.213.152]) by mx.google.com with ESMTPS id hk9sm11230946qab.20.2012.02.15.07.38.43 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 15 Feb 2012 07:38:43 -0800 (PST) From: Aaron Cordova Mime-Version: 1.0 (Apple Message framework v1257) Content-Type: multipart/alternative; boundary="Apple-Mail=_63BEB599-A616-4C66-B280-C35512A5F23A" Subject: Re: Suspension Date: Wed, 15 Feb 2012 10:38:41 -0500 In-Reply-To: To: accumulo-user@incubator.apache.org References: <725648BA-38D2-4C3E-8F19-8DFB4850ED41@cordovas.org> <76326952.68234.1329319609926.JavaMail.root@linzimmb04o.imo.intelink.gov> Message-Id: X-Mailer: Apple Mail (2.1257) X-Gm-Message-State: ALoCoQmP10BAnzzYACbsd0WLzdXPF8/EaOb3jMzjSeAlQfMTtFxGDX4GAlOcinTkRH8lh8PEfTxn --Apple-Mail=_63BEB599-A616-4C66-B280-C35512A5F23A Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 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? >=20 > 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 start-all.sh. >=20 > 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. >=20 > Adam >=20 >=20 > 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. >=20 > Does it make sense to make it possible to suspend a running Accumulo = instance, or should this simply be discouraged and made well known? >=20 >=20 --Apple-Mail=_63BEB599-A616-4C66-B280-C35512A5F23A Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1 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" <adam.p.fuchs@ugov.gov> 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 start-all.sh.

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 <aaron@cordovas.org> 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?



--Apple-Mail=_63BEB599-A616-4C66-B280-C35512A5F23A--