Skip to content
This repository has been archived by the owner on Aug 13, 2024. It is now read-only.

Add job heartbeat as webhook event #99

Open
alexanderdean opened this issue Jan 26, 2017 · 2 comments
Open

Add job heartbeat as webhook event #99

alexanderdean opened this issue Jan 26, 2017 · 2 comments
Milestone

Comments

@alexanderdean
Copy link
Contributor

Configurable frequency but default to 5 minutes.

This is useful for the Factotum UI because if you have a very long-running job node (like a whole EMR jobflow), then there's no way of knowing that that DAG is still ongoing (because you're not getting any job updates, and you're not getting any task updates).

@alexanderdean alexanderdean added this to the Version 0.5.0 milestone Jan 26, 2017
@alexanderdean alexanderdean changed the title Add job heartbeat as webhook Add job heartbeat as webhook event Jan 26, 2017
@ninjabear
Copy link
Contributor

A job is ongoing if there's a "started" but not a "finished" no? Is this related to #94 ?

@alexanderdean
Copy link
Contributor Author

A job is ongoing if:

  • There's a "started" but not a "finished", and
  • the server running the job is still operational, and
  • all webhooks have been correctly sent by Factotum

So it's a fragile assumption. Once we have the heartbeat, the job is ongoing if we continue to receive heartbeats every X minutes.

@ungn ungn removed their assignment Jun 5, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants