- 01 Aug, 2017 2 commits
-
-
Morris Jette authored
Highlight the need to use Slurm abstract CPU ID
-
Alejandro Sanchez authored
When the node isn't actually rebooted, the BootTime isn't updated and Slurm doesn't consider that the node is returned to service, even if slurmd is responding. Bug 4039
-
- 31 Jul, 2017 1 commit
-
-
Tim Shaw authored
This will be fixed before 17.11, but is being left as-is on 17.02. Bug 3956.
-
- 28 Jul, 2017 5 commits
-
-
Danny Auble authored
to have 'socket=' in AuthInfo to work. This is to make it so people don't have to update their slurmdbd.conf's when upgrading (and to match documentation). Continuation of last commit Bug 4009
-
Danny Auble authored
connection. Bug 4009
-
Alejandro Sanchez authored
jobcomp/elasticsearch saves/load the state to/from elasticsearch_state. Since the jobcomp API isn't designed with save/load state operations, the plugin _save_state() isn't extern and not available from outside the plugin itself, thus it is highly coupled to fini() function. This state doesn't follow the same execution path as the rest of Slurm states, where in save_all_sate() they are all independently scheduled. So we save it manually here on a RPC of type REQUEST_CONTROL. This enables that when the Primary ctld issues a REQUEST_CONTROL to the Backup which is currently in controller mode, the Backup will save the state and when the Primary assumes control again it can process the saved pending jobs. The other way around was already controlled, because when the Primary is running in controller mode and the Backup issues a REQUEST_CONTROL, the Primary is shutdown and when breaking the ctld main() function while(1) loop, there was already a g_slurm_jobcomp_fini() call in place. Bug 3908
-
Dominik Bartkiewicz authored
-
Dominik Bartkiewicz authored
Bug 3973.
-
- 27 Jul, 2017 2 commits
-
-
Alejandro Sanchez authored
When more than 1 ping cycle is spawned simultaneously (for instance REQUEST_PING + REQUEST_NODE_REGISTRATION_STATUS for the selected nodes), we do not track a separate ping_start time for each cycle. When ping_begin() is called, the information about the previous ping cycle is lost. Then when ping_end() is called for the first of the two cycles, we set ping_start=0, which is incorrectly used to see if the last cycle ran for more than PING_TIMEOUT seconds (100s), thus incorrectly triggering the: error("Node ping apparently hung, many nodes may be DOWN or configured " "SlurmdTimeout should be increased"); Bug 3914
-
Tim Shaw authored
Bug 3941.
-
- 26 Jul, 2017 5 commits
-
-
Danny Auble authored
-
Danny Auble authored
-
Danny Auble authored
Get rid of any race conditions and call anything that was in _pre_task_privileged from the parent instead of the child. NOTE: This should be safe as we don't execute the task until after _exec_wait_child_wait_for_parent is signaled which happens after all this is long over.
-
Danny Auble authored
Bug 3865
-
Dominik Bartkiewicz authored
Fix regression in commit e5c05549 that would put the stepd pid into the memory cgroup instead of the task's pid. Beforehand this would put the result of getpid() into the cgroup. Before e5c05549 this was done in the child of the fork which would get you the task's pid, but moving it to run in the parent broke this logic. What this patch does is adds pid to the input parameters of task_g_pre_launch_priv making it so we could use the correct pid.
-
- 25 Jul, 2017 1 commit
-
-
Morris Jette authored
-
- 24 Jul, 2017 3 commits
-
-
Morris Jette authored
-
Danny Auble authored
-
Danny Auble authored
Pretty much fix the entire purpose of this max_agent_queue.
-
- 21 Jul, 2017 3 commits
-
-
Danny Auble authored
Bug 3159
-
Tim Shaw authored
Bug 3956
-
Danny Auble authored
Bug 3967
-
- 19 Jul, 2017 4 commits
-
-
Danny Auble authored
step wasn't always gathered correctly. Bug 3531
-
Morris Jette authored
Fix for possible slurmctld abort with use of salloc/sbatch/srun --gres-flags=enforce-binding option. bug 4008
-
Morris Jette authored
Update from commit b40bd8d3
-
Brian Christiansen authored
Clarify --immediate option.
-
- 18 Jul, 2017 1 commit
-
-
Dominik Bartkiewicz authored
By removing the real locks we can get into a race condition where the prolog starts and finishes before we get here and then we end up waiting forever. Making the mutex a static seemed to help in many cases, but didn't completely close the window. Changing slurm_cond_wait to slurm_cond_timedwait fixed the scenario where we would hit the window, but not degrade performance the original commit provides. There were also spots where if the job or step didn't exist it wouldn't signal the conditional also providing a spot this could get stuck not starting the job. Fix regression from commit 52ce3ff0 Bug 3977
-
- 14 Jul, 2017 3 commits
-
-
Tim Shaw authored
Code provided by Ole Nielsen <Ole.H.Nielsen@fysik.dtu.dk> Bug 3985
-
Danny Auble authored
-
Danny Auble authored
This is a regression from commit fec995e0. It turns out using tok here was erroneous for situations where the gres had a type and name and potentially a count (i.e. network:gigabit:1) _get_gres_req_cnt() would alter the incoming char *config which is what tok was. So when we print it back to the requested string it would only have what was there to the first ':'. As we didn't need to \0 out the first char as we skip over it anyway I just kept track of what the replaced \0 was for the number portion and put it back when we are done copying it. Related to bug 3521
-
- 13 Jul, 2017 7 commits
-
-
Tim Wickberg authored
-
Morris Jette authored
-
Tim Shaw authored
bug 3979
-
Danny Auble authored
Bug 3967
-
Danny Auble authored
Bug 3979 and 3989
-
Danny Auble authored
This reverts commit d49081df.
-
Danny Auble authored
Bug 3979 and 3989
-
- 10 Jul, 2017 1 commit
-
-
Ole H Nielsen authored
-
- 07 Jul, 2017 2 commits
-
-
Danny Auble authored
will have a time displayed when truncating time. Bug 3940.
-
Alejandro Sanchez authored
Otherwise we can end up printing Start times greater than End times, leading to confusion when reading sacct output. 0 is displayed as Unknown. Cosmetic change. Bug 3940.
-