Return-Path: 
 <dev-return-10989-apmail-hama-dev-archive=hama.apache.org@hama.apache.org>
X-Original-To: apmail-hama-dev-archive@www.apache.org
Delivered-To: apmail-hama-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 CE14010527
	for <apmail-hama-dev-archive@www.apache.org>;
 Thu, 18 Jul 2013 09:05:40 +0000 (UTC)
Received: (qmail 3311 invoked by uid 500); 18 Jul 2013 09:05:39 -0000
Delivered-To: apmail-hama-dev-archive@hama.apache.org
Received: (qmail 3238 invoked by uid 500); 18 Jul 2013 09:05:37 -0000
Mailing-List: contact dev-help@hama.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@hama.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@hama.apache.org>
List-Post: <mailto:dev@hama.apache.org>
List-Id: <dev.hama.apache.org>
Reply-To: dev@hama.apache.org
Delivered-To: mailing list dev@hama.apache.org
Received: (qmail 3178 invoked by uid 99); 18 Jul 2013 09:05:36 -0000
Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 18 Jul 2013 09:05:36 +0000
Received: from localhost (HELO mail-vc0-f178.google.com) (127.0.0.1)
  (smtp-auth username surajsmenon, mechanism plain)
  by minotaur.apache.org (qpsmtpd/0.29) with ESMTP;
 Thu, 18 Jul 2013 09:05:35 +0000
Received: by mail-vc0-f178.google.com with SMTP id hr11so1029386vcb.23
        for <dev@hama.apache.org>; Thu, 18 Jul 2013 02:05:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        bh=/9DbAMAM44rM16JSoiEm1cz19F7DwmfBKMe+GXrh8m8=;
        b=PoMV7EHALlc7kyH/bV2WIJFWXFZjO8qA9uxNVKNztfp72YVRrqbDwAHRLYa5Ngjnbc
         wvMYJxlb/tEXoaoK2x3ZCAufzT4+W36R1a+Egant+JGpvwNxOOK43yuqQq4pY5RzNP5z
         A+Im+rB/D6flf2Rij2JEYkOd0rpxFt6b4fCzCc2ZCy4LMjGrOPQ/UJfZK75Ksc2c2VU4
         r0G1OGr4pSidU9xv9EfadbIZz/Y/CKdd+NwYLbwRHfv5xVwCtL6insk0UYK3IAixwhp2
         wjLMEMAt1AYBsAFUNbrRWm0JWH55IcFHBBhzTmslcIAeBNOdgAkg/eR3vrHH0lynd/hD
         dUxg==
MIME-Version: 1.0
X-Received: by 10.52.90.50 with SMTP id bt18mr3101895vdb.35.1374138333853;
 Thu, 18 Jul 2013 02:05:33 -0700 (PDT)
Received: by 10.58.172.129 with HTTP; Thu, 18 Jul 2013 02:05:33 -0700 (PDT)
In-Reply-To: 
 <CAGnSx07BYErVuGvCgpF55EvZpKmRvix8U=FSAOppYC4g5fW29g@mail.gmail.com>
References: 
 <CAGnSx04N=_ke8o=Vx9ApKorK3dfDE_qbYO=-c7axf4FFNrG1Cg@mail.gmail.com>
	<CAGQgZQRYuC9AevXi2HX_AUkPTe22=Q_KoSQtHqcSxfPaud7LtA@mail.gmail.com>
	<CAGnSx07BYErVuGvCgpF55EvZpKmRvix8U=FSAOppYC4g5fW29g@mail.gmail.com>
Date: Thu, 18 Jul 2013 05:05:33 -0400
Message-ID: 
 <CALis4o7E8n5S6s3T+ZbFg+EUZ3C2TFMM+bnA6VA4GSB_dU+aig@mail.gmail.com>
Subject: Re: Issue while using DiskVerticesInfo
From: Suraj Menon <surajsmenon@apache.org>
To: "dev@hama.apache.org" <dev@hama.apache.org>
Content-Type: multipart/alternative; boundary=bcaec50162af4419de04e1c58308

--bcaec50162af4419de04e1c58308
Content-Type: text/plain; charset=ISO-8859-1

I can take a look at it this weekend.

-Suraj


On Wed, Jul 17, 2013 at 6:06 AM, Tommaso Teofili
<tommaso.teofili@gmail.com>wrote:

> Yes, I assumed the DiskVerticesInfo implementation was sorting vertices to
> accomplish that so I wonder if we have a bug there (or, for example, if
> there's something else to configure).
>
> Maybe @Suraj could help?
>
> Thanks in advance,
> Tommaso
>
> 2013/7/17 Edward J. Yoon <edwardyoon@apache.org>
>
> > Hi,
> >
> > Our graph package is a pregel-like vertex-centric programming model,
> > and it allows to communication between "vertices".
> >
> > Internally, each BSP processor performs computations for all assigned
> > vertices.
> >
> >   /**
> >    * The user-defined function
> >    */
> >   public void compute(Iterable<M> messages) throws IOException;
> >
> > To avoid grouping messages in received queue by vertex ID, we uses
> > Sorted Message Queue, and calls user-defined function for each vertex
> > sequentially. By using this sequential processing approach, we reduce
> > the memory usage.
> >
> > The current problem is vertex loading phase (or partitioner). The
> > loaded vertices in memory of each BSP processor should already be
> > sorted by vertex ID. In ListVerticesInfo case,
> >
> >   @Override
> >   public void finishAdditions() {
> >     Collections.sort(vertices);
> >   }
> >
> > This is quick-fix solution. We have to sort the vertices by vertex ID
> > at partitioning or loading phase.
> >
> > On Wed, Jul 17, 2013 at 4:44 PM, Tommaso Teofili
> > <tommaso.teofili@gmail.com> wrote:
> > > Hi all,
> > >
> > > I was trying to run the TestSubmitGraphJob with DiskVerticesInfo and I
> > got
> > > this :
> > >
> > > 13/07/17 09:21:45 INFO graph.GraphJobRunner: 7 vertices are loaded into
> > > 192.168.1.4:61001
> > >
> > > 13/07/17 09:21:45 ERROR bsp.BSPTask: Error running bsp setup and bsp
> > > function.
> > > java.lang.IllegalArgumentException: Messages must never be behind the
> > > vertex in ID! Current Message ID: facebook.com vs. stackoverflow.com
> > >  at
> org.apache.hama.graph.GraphJobRunner.iterate(GraphJobRunner.java:281)
> > > at
> > org.apache.hama.graph.GraphJobRunner.doSuperstep(GraphJobRunner.java:229)
> > >  at org.apache.hama.graph.GraphJobRunner.bsp(GraphJobRunner.java:133)
> > > at org.apache.hama.bsp.BSPTask.runBSP(BSPTask.java:177)
> > >  at org.apache.hama.bsp.BSPTask.run(BSPTask.java:146)
> > > at
> > org.apache.hama.bsp.GroomServer$BSPPeerChild.main(GroomServer.java:1262)
> > >
> > > 13/07/17 09:21:45 INFO server.PrepRequestProcessor: Processed session
> > > termination for sessionid: 0x13feb81547f0003
> > >
> > > 13/07/17 09:21:45 INFO server.NIOServerCnxn: Closed socket connection
> for
> > > client /0:0:0:0:0:0:0:1%0:51900 which had sessionid 0x13feb81547f0003
> > >
> > >
> > > Does anyone know what could be the root cause of such a failure?
> > >
> > > Thanks a lot in advance,
> > > Tommaso
> >
> >
> >
> > --
> > Best Regards, Edward J. Yoon
> > @eddieyoon
> >
>

--bcaec50162af4419de04e1c58308--