Return-Path: X-Original-To: apmail-hama-user-archive@www.apache.org Delivered-To: apmail-hama-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 019B110883 for ; Sun, 19 Jan 2014 20:38:11 +0000 (UTC) Received: (qmail 92548 invoked by uid 500); 19 Jan 2014 20:38:10 -0000 Delivered-To: apmail-hama-user-archive@hama.apache.org Received: (qmail 92500 invoked by uid 500); 19 Jan 2014 20:38:09 -0000 Mailing-List: contact user-help@hama.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hama.apache.org Delivered-To: mailing list user@hama.apache.org Received: (qmail 92489 invoked by uid 99); 19 Jan 2014 20:38:09 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Jan 2014 20:38:09 +0000 Received: from localhost (HELO mail-ob0-f175.google.com) (127.0.0.1) (smtp-auth username surajsmenon, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Sun, 19 Jan 2014 20:38:08 +0000 Received: by mail-ob0-f175.google.com with SMTP id wn1so834183obc.20 for ; Sun, 19 Jan 2014 12:38:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Snoyrh+555rcUCTpmlHqC7lsJCYsKruRP+LFrp/I5nk=; b=Y2kP5qITgFLQN9Zo3CYAQ1eElQMZfh+WEvxk1RFopJzDXY3S05xruKvJlfGlf1IGzC h+MVNozB338v2G4EZGbChAsgiATR2M/EH8Je98jNy4JZ5VAsmIYhkTIexA1zVHwKoY01 VagEuUZGmR2nDvqa2rrW/tpmgONWBOpQvh4a5xegJansx6n0MjN+IZGpNRCgmkJPu6+c 4YiGXNftIRyZVmD12BYwwpzElUE9XRm6aX1yRuM04DN9cttJb1U/4ZfArTsJZCi1kZmr xOjF7ZWYC1nA7VWB70PoLMFIvwXEFrpMboP3ohXSsDJv8XOGR/X/rLvLiR5Q37CPwNp5 YbYw== MIME-Version: 1.0 X-Received: by 10.182.196.3 with SMTP id ii3mr12291676obc.11.1390163888078; Sun, 19 Jan 2014 12:38:08 -0800 (PST) Received: by 10.76.156.129 with HTTP; Sun, 19 Jan 2014 12:38:08 -0800 (PST) In-Reply-To: References: Date: Sun, 19 Jan 2014 15:38:08 -0500 Message-ID: Subject: Re: how to get the number of supersteps between peers on evey datanode From: Suraj Menon To: "user@hama.apache.org" Content-Type: multipart/alternative; boundary=089e015383e4ba88ed04f058c0fc --089e015383e4ba88ed04f058c0fc Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I am not sure if I have understood your question correctly. As per the current state of implementation, all peers go through the same number of supersteps and at an instant of time all peers would be executing the same superstep sequece. (i.e. get superstep number API call should give the same number on all peers executing a task) Hope I have answered your question. -Suraj On Sat, Jan 11, 2014 at 10:28 PM, =E5=BA=B7=E9=9B=AA=E4=B8=B9 wrote: > Hello, I need to know about the number of supersteps between peers o= n > every datanode,now i can just get the all number of supersteps of one ta= sk > through the hama API.just like this:The total number of supersteps:63. > Could you help me to solve this problem? > Thanks. > Best wishes. --089e015383e4ba88ed04f058c0fc--