Bug 6004

Update seff to reflect API change from rss_max to tres_usage_in_max. Use
Slurmdb::find_tres_count_in_string to parse out the TRES_MEM value.

Bug 6004

Bug 5736

This check really is there to test if we have dynamic(inactive) features.

Obviously this doesn't work on heterogeneous systems, but there is no
good way to check for this as this check is used long before nodes are
considered.

Bug 6242

Docs updated with details. 'node' is simply removed from the tres list;
the report will continue if other valid tres are specified.

Bug 5954

Bug 6356.

Fixed srun from double printing invalid option
msg twice. Also removed the unused -b flag from sbatch.

Bug 6356.

This patch fixes the regression caused by 07483564 where only the
linux plugin was handling this scenario correctly.

Bug 6332

Bug 6331

Add a debug statement.

Bug 5823

When the backup slurmdbd is active, there is no need to print
connection errors every 10 minutes when the backup checks in on the
primary, at least at the 'error' level.

Prevent dbd clients, like sacctmgr, from printing a connection error
when running commands against the backup slurmdbd unless debug2.
Before, the clients would always print errors when trying to access
the primary dbd first.

Bug 5823

Fix issue introduced in commit 164d4878 that avoided a job to be modified
setting the current reservation to none.

Bug 6309

which caused negative values and values starting with a decimal
to be invalid for PriorityWeightTRES and TRESBillingWeight.

Bug 6217

Bug 6321

As pthread_rwlock_t is a struct, we cannot use this syntax
to initialize all elements of the array to the same value
as we would if these were any basic type.

Instead, move the initialization to a dedicated loop to ensure
all locks are initialized correctly.

This does not seem to have caused any issues on Linux platforms,
but macOS at least does notice this mistake.

Bug 6319.

Enabling this alters the scheduling sorting algorithm so that hetjob
components belonging to the same hetjob are attempted to be scheduled
consecutively (not interleaved with other jobs or hetjob components).

Bug 5579.

AccrueTime limits.

Bug 6002


Co-authored-by: Felip Moll <felip.moll@schedmd.com>

Regression introduced in ccafaf7b.

Replace the (was always set to true) check_current_dir argument to
search_path() with check_cwd_last boolean to indicate if cwd should be
evaluated first (needed by sbatch) or last (salloc/srun).

Bug 6271.

Bug 6169

Bug 6289

Introduced in d9b9eb23

Bug 6292

Bug 5441

Co-authored-by: Felip Moll <felip.moll@schedmd.com>
Co-authored-by: Danny Auble <da@schedmd.com>

Bug 5441

Bug 5971

from a node.

Bug 5971

Bug 6229

Bug 6239

backport of 03ada72e

Bug 5682

Bug 5682 and 4584

Backport of ba07a6e09b6071

other than knl.

Bug 5603

Bug 5603

This patch also simplifies the code using bit_cnt instead of
_bitstr_bits().  This isn't really necessary, but does look cleaner.

Bug 6216

It was using the local cluster, sending the query to the wrong table

Bug 6159

Bug 6237

if OverTimeLimit is Unlimited.

Bug 6093

Only print a warning for 18.08. If a user has SLURM_MEM_PER_CPU or
SLURM_MEM_PER_NODE environment variables set for some reason this
situation could be happening by accident, and we don't want to prevent
the srun command from launching steps at this point.

Bug 6058.

Bug 5648.

The Linux kernel default hard limit of 4096 for the number of file
descriptors is quite small. Debian/Ubuntu have for a long time
overridden this, increasing it to 1M. Recently systemd also bumped the
default to 512k.

https://github.com/systemd/systemd/blob/master/NEWS

https://github.com/systemd/systemd/pull/10244

https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/ZN5TK3D6L7SE46KGXICUKLKPX2LQISVX/

https://github.com/systemd/systemd/commit/09dad04c49cae3ad2b319c9b4e7773fedd34309a

Here the limits are increased as follows:

- slurmd: 128k; some workloads like Hadoop/Spark need a lot of fd's,
  and recommend that the limit is increased to at least 64k.

- slurmctld: 64k; per the Slurm high throughput and big system guides
  which recommend a file-max of at least 32k.

- slurmdbd: 64k, matching slurmctld, though slurmdbd shouldn't need
  that many fd's, bumping the limit shouldn't hurt either.

Bug 6171

Bug 5248