[Iplant-api-dev] Job events

[Duvick, Jonathan P [GDCBS]]

Yes, STOPPED notification was sent this time. I was getting a lot of 500 server errors last night as well, and some funny responses where http_code=200 but no 'success' status was returned.

Maybe we can blame the out of memory issues for that as well.

Thanks!


Jon Duvick
PlantGDB Manager
http://www.plantgdb.org/
Department of Genetics, Development and Cell Biology
2258 Molecular Biology Building
Iowa State University
Ames IA 50011

(515) 294-2360
(515) 294-6755 FAX
________________________________
From: Rion Dooley <dooley at tacc.utexas.edu>
Sent: Sunday, March 1, 2015 11:55 PM
To: Duvick, Jonathan P [GDCBS]
Cc: iPlant API Developers Mailing List
Subject: Re: [Iplant-api-dev] Job events

I'm working on the Jobs api right now anyways. I'll add some more tests to validate the expected callback behavior. I think the reason you didn't get a STOPPED event was that our message queue blew through it's memory limit sometime in the last hour or two. I restarted it and your job (0001425272937014-5056a550b8-0001-007), then stopped your job again and I'm seeing the notification being sent in our logs. Can you verify you got it this time?

I've noticed this happen a few times over the past month and part of the coming updated is that we are moving our message queue to Iron.io. This should reduce the number of missed events and let us scale better across and within data centers based on a normalized event volume rather than just traffic.

-
Rion

On Mar 1, 2015, at 11:33 PM, Duvick, Jonathan P [GDCBS] <jduvick at iastate.edu<mailto:jduvick at iastate.edu>> wrote:

Thanks for the clarification on STOPPED vs KILLED.
POSTing "action":"stop" works fine for me, although in my trials thus far the server fails to send a STOPPED or KILLED status update to my callback URL (webhook)
All other status changes (e.g. RUNNING, ARCHIVING) are sent as expected.
Not sure what you mean about POSTing manually to my web hook URL.

Jon Duvick
PlantGDB Manager
http://www.plantgdb.org/
Department of Genetics, Development and Cell Biology
2258 Molecular Biology Building
Iowa State University
Ames IA 50011

(515) 294-2360
(515) 294-6755 FAX
________________________________
From: Rion Dooley <dooley at tacc.utexas.edu<mailto:dooley at tacc.utexas.edu>>
Sent: Sunday, March 1, 2015 10:14 PM
To: Duvick, Jonathan P [GDCBS]
Cc: iPlant API Developers Mailing List
Subject: Re: [Iplant-api-dev] Job events

Hi Jon,

Pausing and checkpointing jobs is highly dependent on the underlying system and, at the moment, I'm unaware of any systems that will actually allow you to pull that off reliably.

You can make a POST request to a specific job resource with a form of action="stop" or a content type of application/json and body of

{ "action":"stop" }

That will kill a running job or cancel a submitted job. The former will cause a KILLED event to fire. The latter will cause a STOPPED event to fire. If you're testing out webhooks as part of your application, you can, of course, just manually POST to your web hook URL to emulate the behavior.

-
Rion

On Mar 1, 2015, at 9:52 PM, Duvick, Jonathan P [GDCBS] <jduvick at iastate.edu<mailto:jduvick at iastate.edu>> wrote:

Can I effect these event states via the API?
-KILLED Job execution killed at user request
-PAUSED Job execution paused by user
How are the dependencies and outcomes different from STOPPED?

(http://preview.agaveapi.co/documentation/event-reference/)

Thanks,

Jon Duvick
PlantGDB Manager
http://www.plantgdb.org/
Department of Genetics, Development and Cell Biology
2258 Molecular Biology Building
Iowa State University
Ames IA 50011

(515) 294-2360
(515) 294-6755 FAX
_______________________________________________
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/20150302/aa6ab252/attachment-0001.html