Return-Path: X-Original-To: apmail-airavata-dev-archive@www.apache.org Delivered-To: apmail-airavata-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 ADB62178A4 for ; Fri, 24 Apr 2015 17:56:26 +0000 (UTC) Received: (qmail 40405 invoked by uid 500); 24 Apr 2015 17:56:26 -0000 Delivered-To: apmail-airavata-dev-archive@airavata.apache.org Received: (qmail 40356 invoked by uid 500); 24 Apr 2015 17:56:26 -0000 Mailing-List: contact dev-help@airavata.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@airavata.apache.org Delivered-To: mailing list dev@airavata.apache.org Received: (qmail 40341 invoked by uid 99); 24 Apr 2015 17:56:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2015 17:56:26 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: message received from 54.164.171.186 which is an MX secondary for dev@airavata.apache.org) Received: from [54.164.171.186] (HELO mx1-us-east.apache.org) (54.164.171.186) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Apr 2015 17:56:20 +0000 Received: from mail-oi0-f45.google.com (mail-oi0-f45.google.com [209.85.218.45]) by mx1-us-east.apache.org (ASF Mail Server at mx1-us-east.apache.org) with ESMTPS id 53EFB43E41 for ; Fri, 24 Apr 2015 17:55:50 +0000 (UTC) Received: by oift201 with SMTP id t201so46690628oif.3 for ; Fri, 24 Apr 2015 10:55:05 -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=7N6i06NxFkuGOd2+EicRdiR7uXeWNQ9OaW7igivcXY0=; b=p0/eHBWOBoWOBMVI0kXaqYr1OtHilx4Umo3GK6idJ8VqucQ1dhngAHw+frtv7bux2N z+HF/3MM+qMn6U3BD3nLGOCGDbcCBO7fWa8qcgO7dFSwEeaTeCeMsn7HCz+As3g5Ylht ZYh4FRxPspSZ8iDVEUbr7otARYhNtRnapBUCWpzvmFdBnb0EklFIKbe9deLPUl2yNeCb LBxwYWFpdytLSJYTzl109N5y7ExUlFhWI6X9s+9Ap1TiIfqILgOCPF+LGI8RNq3z5ToH v8tcImx0FC6kAoqqEyYw0eGgyV+i3kiMNBQKZiiGLk/X+sh/n4FMkOqVXCAdxYAJ1KLU hzTQ== MIME-Version: 1.0 X-Received: by 10.202.69.212 with SMTP id s203mr7970970oia.70.1429898104948; Fri, 24 Apr 2015 10:55:04 -0700 (PDT) Received: by 10.60.144.7 with HTTP; Fri, 24 Apr 2015 10:55:04 -0700 (PDT) In-Reply-To: <1B7F2F06-BF46-4982-8A62-0554E428378C@illinois.edu> References: <1B7F2F06-BF46-4982-8A62-0554E428378C@illinois.edu> Date: Fri, 24 Apr 2015 13:55:04 -0400 Message-ID: Subject: Re: Monitor jobs by JobName if JobId is null From: Lahiru Ginnaliya Gamathige To: dev Content-Type: multipart/alternative; boundary=001a113dd3d89c4cc105147c18e7 X-Virus-Checked: Checked by ClamAV on apache.org --001a113dd3d89c4cc105147c18e7 Content-Type: text/plain; charset=UTF-8 Hi Sudhakar, Of course if its an error we identify that from standard Error and make the job fail but we have seen qsub and sbatch doesn't return jobId but job is actually submitted and we can identify these by parsing the standard error. If standard error is good and we got nothing in jobId we proceed and do the monitoring (pull based monitoring) so thats why we are using jobName instead of jobId. Shameera, JobName is Airavata generated random value so it will be unique like jobId and only good thing with jobName is we already know it and we can avoid relying on the qsub or any other commands output to do the monitoring. Lahiru On Fri, Apr 24, 2015 at 1:47 PM, Pamidighantam, Sudhakar V < spamidig@illinois.edu> wrote: > If jobid is missing due to error job name will not work. > > Sudhakar. > > On Apr 24, 2015, at 12:32 PM, Shameera Rathnayaka > wrote: > > Hi all, > > There is a chance that we will not get jobId after we submit a job to a > compute resoruce. In that case we can use JobName to monitor the Job using > email based monitor. I am going to do that fix on master, if there is no > jobId then we use JobName as the job monitor key. > > Thanks, > Shameera. > > -- > Best Regards, > Shameera Rathnayaka. > > email: shameera AT apache.org , shameerainfo AT gmail.com > Blog : http://shameerarathnayaka.blogspot.com/ > > > -- Research Assistant Science Gateways Group Indiana University --001a113dd3d89c4cc105147c18e7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi Sudhakar,

Of course if its an = error we identify that from standard Error and make the job fail but we hav= e seen qsub and sbatch doesn't return jobId but job is actually submitt= ed and we can identify these by parsing the standard error. If standard err= or is good and we got nothing in jobId we proceed and do the monitoring (pu= ll based monitoring) so thats why we are using jobName instead of jobId.=C2= =A0

Shameera, JobName is Airavata generated random value= so it will be unique like jobId and only good thing with jobName is we alr= eady know it and we can avoid relying on the qsub or any other commands out= put to do the monitoring.

Lahiru

On Fri, Apr 24, 2015 at= 1:47 PM, Pamidighantam, Sudhakar V <spamidig@illinois.edu> wrote:
If jobid is missing due to error job name will not work.=C2=A0

<= span class=3D"HOEnZb">Sudhakar.
<= div class=3D"h5">
On Apr 24, 2015, at 12:32 PM, Shameera Rathn= ayaka <shame= erainfo@gmail.com> wrote:

Hi all,=C2= =A0

<= div class=3D"gmail_default" style=3D"font-size:small">There is a chance tha= t we will not get jobId after we submit a job to a compute resoruce. In tha= t case we can use JobName to monitor the Job using email based monitor. I a= m going to do that fix on master, if there is no jobId then we use JobName = as the job monitor key.=C2=A0

Thanks,
Sh= ameera.=C2=A0

--
Best Regards,
Shameera Rathnayaka.

email: = shameera AT apache.org= , shameerainfo AT gmail.co= m
Blog : http://shameerarathnayaka.blog= spot.com/




--
Research Assistant=C2=A0
Science Gateways Group
Indi= ana University
--001a113dd3d89c4cc105147c18e7--