Return-Path: X-Original-To: apmail-giraph-dev-archive@www.apache.org Delivered-To: apmail-giraph-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 78BA0DF63 for ; Mon, 24 Sep 2012 18:08:08 +0000 (UTC) Received: (qmail 50766 invoked by uid 500); 24 Sep 2012 18:08:08 -0000 Delivered-To: apmail-giraph-dev-archive@giraph.apache.org Received: (qmail 50731 invoked by uid 500); 24 Sep 2012 18:08:08 -0000 Mailing-List: contact dev-help@giraph.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@giraph.apache.org Delivered-To: mailing list dev@giraph.apache.org Received: (qmail 50723 invoked by uid 99); 24 Sep 2012 18:08:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2012 18:08:08 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of apache.mailbox@gmail.com designates 209.85.216.52 as permitted sender) Received: from [209.85.216.52] (HELO mail-qa0-f52.google.com) (209.85.216.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 24 Sep 2012 18:08:01 +0000 Received: by qabg24 with SMTP id g24so2842825qab.11 for ; Mon, 24 Sep 2012 11:07:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=JafIDaawIy1ZKNBzpKKxGrSQ+tCLMjX2MB8FjfJvYX8=; b=BBqk+Qr77UMDS/9Xr3PU4JlZcNfh0cnK6nvgwyiYpT2duS2c+YxKPfqzX+tL2B4EJ1 HIIWkHLmMMny+FfZsJCL67Mu5SLYDGQM2Z7t8UoPiwEFx8hoz4+PC22Y6hvOXusmM4SN ivZn0GpOyTqCMjoyJ8X9IIMsA5llae/K7SW4zU+Ga0fJOV9Yk61faJBfHVvYRPZarpS3 BmNe5/cK8+OqmUWHCXlmcGBYFAzqrH80WaIXZTY1mgGGCJBD0b85tP4WYGXtAd8sP+Pu /Cx5l8UWiDgrJmvKd5t11drZyVKVPYLql+QvU7ro4DIzACYklxh5uoBkIRDY0RYjat+y b59g== MIME-Version: 1.0 Received: by 10.229.137.85 with SMTP id v21mr9231248qct.17.1348510060728; Mon, 24 Sep 2012 11:07:40 -0700 (PDT) Received: by 10.49.15.129 with HTTP; Mon, 24 Sep 2012 11:07:40 -0700 (PDT) In-Reply-To: <962352966.100141.1348097108652.JavaMail.jiratomcat@arcas> References: <2002219.153.1344433461103.JavaMail.jiratomcat@issues-vm> <962352966.100141.1348097108652.JavaMail.jiratomcat@arcas> Date: Mon, 24 Sep 2012 11:07:40 -0700 Message-ID: Subject: Re: [jira] [Commented] (GIRAPH-293) Should aggregators be checkpointed? From: Eli Reisman To: dev@giraph.apache.org Content-Type: multipart/alternative; boundary=00235452e96025508004ca767798 --00235452e96025508004ca767798 Content-Type: text/plain; charset=ISO-8859-1 Sorry I ended up out of the loop this week, sounds good to me too! On Wed, Sep 19, 2012 at 4:25 PM, Avery Ching (JIRA) wrote: > > [ > https://issues.apache.org/jira/browse/GIRAPH-293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13459210#comment-13459210] > > Avery Ching commented on GIRAPH-293: > ------------------------------------ > > +1. This is Any objections Eli? > > > Should aggregators be checkpointed? > > ----------------------------------- > > > > Key: GIRAPH-293 > > URL: https://issues.apache.org/jira/browse/GIRAPH-293 > > Project: Giraph > > Issue Type: Bug > > Reporter: Alessandro Presta > > Assignee: Maja Kabiljo > > Attachments: GIRAPH-293.patch, GIRAPH-293.patch, > GIRAPH-293.patch, GIRAPH-293.patch > > > > > > As I understand, we don't include aggregators in checkpoints because > they are kept in the Zookeeper. > > One of our bootcampers is working on fixing TestManualCheckpoint, which > currently involves starting a new job from a checkpoint from a previous > job*. > > If this is a functionality we want going forward, then persistent > aggregators should be checkpointed. > > [*] That test relies on the fact that either aggregators are > checkpointed or they are always reset at each superstep. None of these is > happening, but the error cancels out with the fact that we are not actually > resuming from a checkpoint, but re-running the job from scratch. > > -- > This message is automatically generated by JIRA. > If you think it was sent incorrectly, please contact your JIRA > administrators > For more information on JIRA, see: http://www.atlassian.com/software/jira > --00235452e96025508004ca767798--