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

Nomad should start system jobs with more higher priority than service jobs. #25061

Closed
EugenKon opened this issue Feb 7, 2025 · 2 comments
Closed
Labels

Comments

@EugenKon
Copy link

EugenKon commented Feb 7, 2025

Nomad version

1.8.2

Operating system and Environment details

Ubuntu 24.04

Issue

This belongs to #25058. That issue is about Nomad problem not reporting that some essential system! jobs were not started. (this is not Ok, that Nomad silently do not run configured jobs).

But this issue is about that Nomad do not start system essentials jobs at all.

Nomad should start all system jobs, then start service jobs after that.

How to reproduce

configure system and service jobs. Though system jobs do not have any constraints the service jobs does and they took whole memory on the instance. Thus there is no room for the system job.

As the result we have working node at the cluster which run tasks without essential system jobs. In this particular case dd-agent was not run and thus this host becomes unmonitored.

TODO

Please report the jobs which are not started properly. See the related issue #25058
Please start system jobs first, then start service jobs.

@tgross
Copy link
Member

tgross commented Feb 7, 2025

@EugenKon you were already told how to solve this problem in #25038. This is working as intended. Just because you happen to have system jobs that are high priority doesn't mean all users do, which is why you must set the priority as you were told there. Also, could you please stop opening new issues instead of continuing a discussion in the original issue? It's annoying to have to spread out a discussion across issues and takes up more of our time.

@tgross tgross closed this as completed Feb 7, 2025
@EugenKon
Copy link
Author

EugenKon commented Feb 7, 2025

Sorry, I did not get notification from that. Do all notifications do not come from your comments as well as I can not type @tgross? @TGro

Image

Sorry once more. This is hard to have all issues opened and track changes there. ((
(I do not have such issues with other repositories)

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

No branches or pull requests

2 participants