[Feature] For nomad status to report on task-groups that are yet to be allocated
#1154
Labels
Comments
|
And here's what I mean by consuming disk space: This is after running ~2600 tasks. |
|
Hey @dvusboy, as mentioned earlier we will address this soon. Will update ticket when something lands in master. |
|
Thanks. I just wanted to capture both points: the snapshot issue, and the signal-to-noise issue. |
|
Awesome! Thanks. |
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In my use case, I have batch jobs set up as a collection of tasks, each wrapped in a task-group to spread out the load across the cluster. Each task takes from 30 minutes to about an hour to complete. When the cluster is fully loaded, new allocations would keep failing and a typical output of
nomad statuslooks like this:There are a number of problems with this:
failedlines, you don't get a sense of the backlog any more, like this:Desiredshouldn't sayfailed, should it?Instead of enumerating each individual failed allocation, I'd be far more interested in those task-groups that are still awaiting a successful allocation.
The text was updated successfully, but these errors were encountered: