Return-Path: 
 <user-return-2265-apmail-giraph-user-archive=giraph.apache.org@giraph.apache.org>
X-Original-To: apmail-giraph-user-archive@www.apache.org
Delivered-To: apmail-giraph-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 19D5910326
	for <apmail-giraph-user-archive@www.apache.org>;
 Thu,  6 Mar 2014 05:54:37 +0000 (UTC)
Received: (qmail 3809 invoked by uid 500); 6 Mar 2014 05:54:29 -0000
Delivered-To: apmail-giraph-user-archive@giraph.apache.org
Received: (qmail 3737 invoked by uid 500); 6 Mar 2014 05:54:22 -0000
Mailing-List: contact user-help@giraph.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@giraph.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@giraph.apache.org>
List-Post: <mailto:user@giraph.apache.org>
List-Id: <user.giraph.apache.org>
Reply-To: user@giraph.apache.org
Delivered-To: mailing list user@giraph.apache.org
Received: (qmail 3695 invoked by uid 99); 6 Mar 2014 05:54:20 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Mar 2014 05:54:20 +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 pankajiitdyn@gmail.com
 designates 209.85.160.170 as permitted sender)
Received: from [209.85.160.170] (HELO mail-yk0-f170.google.com)
 (209.85.160.170)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Mar 2014 05:54:14 +0000
Received: by mail-yk0-f170.google.com with SMTP id 9so5562605ykp.1
        for <user@giraph.apache.org>; Wed, 05 Mar 2014 21:53:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=I4Lu/Gk/TipzibbPzxIKlgC/8UYMDVNp8NW+5al25Dc=;
        b=XVBCrzwq5ScFDKTiFg/ecDebW9zlQM/Fbyk2/H2x0mkbk5z16mkOC83Fsw2Zo3WfTd
         UqsiZx1SY2vGtwzy81XUZv8Fj3Fd2f46pGbzzMwARlOqVXfmXDQPSsKy0msTdSL/cRsI
         OdHahSso0GIYok+LUaRUnGlW1QmyqnswFshYDqlwLl1JU/mPBAD+cY+NTSTrS/K5xx+c
         I9dbm5OB8PEnZXtuk8Zhukty9hfQKECfyCCYEKjushDIXyd7rkuFX+IrGan38eeUo30U
         xvpzaC4N9GMl+uv2MXMQxt+F+WftcaNuQpjbA8UBkr0QPzh9QXWdtwcLoGcN13Hnx+cD
         HsMA==
X-Received: by 10.236.123.193 with SMTP id v41mr12373840yhh.68.1394085233278;
 Wed, 05 Mar 2014 21:53:53 -0800 (PST)
MIME-Version: 1.0
Received: by 10.170.212.69 with HTTP; Wed, 5 Mar 2014 21:53:33 -0800 (PST)
From: Pankaj Malhotra <pankajiitdyn@gmail.com>
Date: Thu, 6 Mar 2014 11:23:33 +0530
Message-ID: 
 <CAMf08QYE+RgUv9otXT6oPJorTNjQ-Ay8p4NUiuhds8+zgDzs1w@mail.gmail.com>
Subject: Is it possible to know the mapper task a particular vertex is
 assigned to?
To: "user@giraph.apache.org" <user@giraph.apache.org>
Content-Type: multipart/alternative; boundary=20cf301afb7b1dc60604f3e9c375
X-Virus-Checked: Checked by ClamAV on apache.org

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

Hi,

How can I find the mapper task a particular vertex is assigned to?
I can do this by doing a sysout and then looking at the logs. But there
must be a smarter way to do this. Please suggest.

Thanks,
Pankaj

--20cf301afb7b1dc60604f3e9c375
Content-Type: text/html; charset=ISO-8859-1

<div dir="ltr">Hi,<div><br></div><div>How can I find the mapper task a particular vertex is assigned to?</div><div>I can do this by doing a sysout and then looking at the logs. But there must be a smarter way to do this. Please suggest.</div>

<div><br></div><div>Thanks,</div><div>Pankaj</div></div>

--20cf301afb7b1dc60604f3e9c375--