Fix for jobs stuck in configuring state in case of the frontend execution mode #186
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
instead of the first node in test_job_nodes_ready function. Otherwise submitted jobs stack in configuring state.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I had a problem running slurm in frontend mode (configured with --enable-front-end) for modeling purposes. Namely, all submitted jobs stay in configuring state:
It turns out that test_job_nodes_ready function from job_mgr.c checking the readiness of the first node for batch job execution. But in frontend mode, it is the task of the frontend node. So I added checking of frontend node instead. That fixed the problem.
Regards,
Nikolay
Used configuration:
slurm.conf