[Iplant-api-dev] irods module

[Rion Dooley]

The queued status of the jobs is simply due to high utilization on Lonestar and the scheduler's fair share policy. Right now there are around 200 jobs running, and 600 in queue. 3 of the running and 40 of the queued jobs are owned by iplant. Lonestar is great at churning through work, so the jobs will run before too long, but in the mean time there isn't really anything we can do but wait our turn.

Rion

________________________________
From: Jennewein, Douglas M [Doug.Jennewein at usd.edu]
Sent: Wednesday, July 31, 2013 11:58 AM
To: Rion Dooley
Cc: development
Subject: RE: irods module

On 7-30 we noticed some jobs failed in the Test Application.  They were not archived, but their output is available (eg /apps-v1/job/19402/output/list ) and appears to show a successful run.  The same runs had completed successfully on 7-29.

We’ve re-submitted them today, 7-31, but they are still queued.

Is this indicative of the recent iRODS problems, or perhaps something else?

Doug



From: iplant-api-dev-bounces at iplantcollaborative.org [mailto:iplant-api-dev-bounces at iplantcollaborative.org] On Behalf Of Rion Dooley
Sent: Tuesday, July 30, 2013 1:57 PM
To: Jennewein, Douglas M
Cc: Ramona Walls; Discussion at mail.iplantcollaborative.org; development
Subject: Re: [Iplant-api-dev] irods module

An update is going out to Lonestar to push the recently updated irods module out to the execution nodes. Siva had a ticket into the admins that is on the list for today's updates.

Rion

________________________________
From: iplant-api-dev-bounces at iplantcollaborative.org<mailto:iplant-api-dev-bounces at iplantcollaborative.org> [iplant-api-dev-bounces at iplantcollaborative.org] on behalf of Barthelson, Roger A - (rogerab) [rogerab at email.arizona.edu]
Sent: Tuesday, July 30, 2013 1:31 PM
To: Rion Dooley
Cc: Ramona Walls; Discussion of iPlant API development
Subject: [Iplant-api-dev] irods module
I am having job failures on Lonestar today because the irods module is not recognized on the execute nodes. On the login node it works fine. It is listed now as "irods". That does not work on the execute nodes. Neither does iRODS. I expect this is killing API jobs on Lonestar.

Roger


Roger Barthelson Ph.D.
Scientific Analyst
iPlant Collaborative
BIO5 Institute, University of Arizona
Phone: 520-977-5249
Email: rogerab at email.arizona.edu<mailto:rogerab at email.arizona.edu>
Web: www.iplantcollaborative.org/<http://www.iplantcollaborative.org/>
           bio-it.arizona.edu/Roger_Barthelson_Home.html

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.iplantcollaborative.org/pipermail/iplant-api-dev/attachments/20130731/6e7e7bfd/attachment-0001.html