Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failure Callback #473

Closed
kapil-malik opened this issue Jun 19, 2015 · 5 comments
Closed

Failure Callback #473

kapil-malik opened this issue Jun 19, 2015 · 5 comments

Comments

@kapil-malik
Copy link
Contributor

We have a requirement that whenever a submitted job is over, our REST endpoint should get a callback for the same.
For jobs which are successfully completed, a small dependent job is good to make this work.
However, for failed jobs, the dependent job is not triggered. Is there any way / any plans to support a failure callback endpoint in Chronos?

@kapil-malik
Copy link
Contributor Author

Hi,
Is there any update on this?

@tnachen
Copy link
Member

tnachen commented Aug 8, 2015

@kapil-malik So are you suggesting another chronos job that runs when one of your steps failed?
I think this is going to be very basic functionality that most people will need, let me see if the Chronos team has planned this or perhaps it's already in Chronos.

@tnachen
Copy link
Member

tnachen commented Aug 8, 2015

Also can you perhaps elaborate more at what stage you like a failure job to happen? And what does that failure job features requirements will look like (Another depednency job chain in chronos, with/without schedule, etc) for you?

@kapil-malik
Copy link
Contributor Author

Hi @tnachen
While I am using a dependent job for success callback, ideally I would want to schedule 'Chronos job' only for the application logic. For my usecase, a success / failure callback can be simply a REST callback, something like marathon.
On the other hand, what you mention is also interesting, a way of conditional execution. Job A -> success = Job B, failure = Job C etc. But I believe this will require more work in Chronos (to design and implement all possible ways of conditional execution).

@kapil-malik
Copy link
Contributor Author

Hi @tnachen
I submitted a pull request for this issue. #518
Can you kindly have a look and provide comments / accept it?

Thanks,

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants