| Summary: | Unable to change RealMemory on nodes | ||
|---|---|---|---|
| Product: | Slurm | Reporter: | Simran <simran> |
| Component: | Configuration | Assignee: | Tim Wickberg <tim> |
| Status: | RESOLVED INFOGIVEN | QA Contact: | |
| Severity: | 3 - Medium Impact | ||
| Priority: | --- | ||
| Version: | 17.02.9 | ||
| Hardware: | Linux | ||
| OS: | Linux | ||
| Site: | Genentech (Roche) | Alineos Sites: | --- |
| Atos/Eviden Sites: | --- | Confidential Site: | --- |
| Coreweave sites: | --- | Cray Sites: | --- |
| DS9 clusters: | --- | HPCnow Sites: | --- |
| HPE Sites: | --- | IBM Sites: | --- |
| NOAA SIte: | --- | OCF Sites: | --- |
| Recursion Pharma Sites: | --- | SFW Sites: | --- |
| SNIC sites: | --- | Linux Distro: | --- |
| Machine Name: | CLE Version: | ||
| Version Fixed: | Target Release: | --- | |
| DevPrio: | --- | Emory-Cloud Sites: | --- |
|
Description
Simran
2017-12-06 17:05:12 MST
Looks like this was because FastSchedule was set to 0 instead of 1. After changing this setting we are now good. Feel free to close this request. Regards, -Simran Yep, that would do it. You might also want to look at the MemSpecLimit option as an alternative approach, if you have a reason to use FastSchedule=0. Marking resolved/infogiven. - Tim |