[Iplant-api-dev] archiving failed

[Rion Dooley]

Looks like the job completed as expected and exited normally. The data was archived and is available in the expected archive directory. From what I can tell, the cleanup script running on the execution machine either hiccuped or lost connectivity with the scheduler for a moment, because a race condition seemed to have occurred. The happens a small percentage of the time (~0.1%) in Foundation and usually shows up when the head nodes on stampede get completely overwhelmed. The good news is we have a solution in place. The bad news is that the solution required some rather elaborate rearchitecting of the way job monitoring was done, so we implemented it in Agave. If you’re not planning on moving to Agave any time soon, I’d suggest adding in a quick check of the archive folder any time you see an ARCHIVING_FAILED status to make sure it’s not giving a false negative. If you have any other questions, just let me know.

--
Rion




On Dec 9, 2013, at 3:08 PM, Khalfan, Mohammed <mkhalfan at cshl.edu<mailto:mkhalfan at cshl.edu>> wrote:

Hi Rion,

I’m getting archiving_failed for this job: 35642

What’s the problem here?

Thank you,

Mohammed Khalfan
Bioinformatics Developer
DNA Learning Center
Cold Spring Harbor Laboratory
1 Bungtown Road
Cold Spring Harbor NY 11724
(516)367-5162
www.dnalc.org<http://www.dnalc.org/>

_______________________________________________
Iplant-api-dev Mailing List: Iplant-api-dev at iplantcollaborative.org<mailto:Iplant-api-dev at iplantcollaborative.org>
List Info and Archives: http://mail.iplantcollaborative.org/mailman/listinfo/iplant-api-dev
One-click Unsubscribe: http://mail.iplantcollaborative.org/mailman/options/iplant-api-dev/dooley%40tacc.utexas.edu?unsub=1&unsubconfirm=1

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