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

[question] Detailed Documentation about Task Status and Desired Status #2039

Closed
nicmue opened this issue Nov 29, 2016 · 4 comments
Closed

[question] Detailed Documentation about Task Status and Desired Status #2039

nicmue opened this issue Nov 29, 2016 · 4 comments
Labels
stage/waiting-reply theme/docs Documentation issues and enhancements

Comments

@nicmue
Copy link

nicmue commented Nov 29, 2016

Is there somewhere a detailed documentation of the "status" and "desired" status a task can have? And especially how do they affect the task-group and job status?

const (
	AllocDesiredStatusRun   = "run"   // Allocation should run
	AllocDesiredStatusStop  = "stop"  // Allocation should stop
	AllocDesiredStatusEvict = "evict" // Allocation should stop, and was evicted
)

const (
	AllocClientStatusPending  = "pending"
	AllocClientStatusRunning  = "running"
	AllocClientStatusComplete = "complete"
	AllocClientStatusFailed   = "failed"
	AllocClientStatusLost     = "lost"
)

When I search the codebase I find all possible States but in particular I don't understand the difference between running and complete or when is a task lost and not failed? Is there a correlation between lost and evict?

Thanks in advance.

@dadgar dadgar added the theme/docs Documentation issues and enhancements label Dec 1, 2016
@dadgar
Copy link
Contributor

dadgar commented Dec 1, 2016

Hey I agree we should document this better.

In the mean time to answer your question:

  • Desired status is what the schedulers want the allocation to do
  • Client status is the emergent state of the allocation
  • Running means the tasks are currently running
  • Complete means the tasks finished successfully
  • Failed means the tasks finished but not successfully (non-zero exit code)
  • Lost means the node that was running the tasks has failed or has been partitioned. As such the servers do not know its state.

@stale
Copy link

stale bot commented May 10, 2019

Hey there

Since this issue hasn't had any activity in a while - we're going to automatically close it in 30 days. If you're still seeing this issue with the latest version of Nomad, please respond here and we'll keep this open and take another look at this.

Thanks!

@stale
Copy link

stale bot commented Jun 9, 2019

This issue will be auto-closed because there hasn't been any activity for a few months. Feel free to open a new one if you still experience this problem 👍

@stale stale bot closed this as completed Jun 9, 2019
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Nov 22, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stage/waiting-reply theme/docs Documentation issues and enhancements
Projects
None yet
Development

No branches or pull requests

2 participants