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

Better task lifecycle tracking and client updates #1559

merged 6 commits into from Jun 8, 2017


Copy link

@ssalinas ssalinas commented Jun 2, 2017

Added a new endpoint to get information about a task regardless of its state. In the previous setup, you would need to grab it from the history endpoint if it was inactive or the tasks endpoint if it was active. Now, this will also check pending (in the case that you include a runId).

The new endpoint will return a SingularityTaskState object if the task exists, which will either have the state or a marker that the task is still pending. the id in that object will be a SingularityTaskId if it is active/inactive, or a SingularityPendingTaskId if it is still pending.

I also took the opportunity to update the SingularityClient a bit (/fixes #1430)

@gchomatas this will help with tracking the state of the task. Would you want any additional information about it, or is the state mostly what you would be after?

@ssalinas ssalinas modified the milestone: 0.16.0 Jun 8, 2017
@ssalinas ssalinas merged commit 8c8e810 into master Jun 8, 2017
@ssalinas ssalinas deleted the task_lifecycle branch June 8, 2017 16:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.

Executor cleanup can't connect to https service endpoint
1 participant