Skip to content

Releases: aws/aws-parallelcluster-node

AWS ParallelCluster v3.7.2

13 Oct 19:37
Compare
Choose a tag to compare

We're excited to announce the release of AWS ParallelCluster Node 3.7.2

This is associated with AWS ParallelCluster v3.7.2

CHANGES

  • There were no changes for this version.

AWS ParallelCluster v3.7.1

22 Sep 20:16
Compare
Choose a tag to compare

We're excited to announce the release of AWS ParallelCluster Node 3.7.1

This is associated with AWS ParallelCluster v3.7.1

CHANGES

  • There were no changes for this version.

AWS ParallelCluster v3.7.0

30 Aug 12:11
Compare
Choose a tag to compare

We're excited to announce the release of AWS ParallelCluster Node 3.7.0

This is associated with AWS ParallelCluster v3.7.0

CHANGES

  • Perform default job-level scaling for exclusive jobs, by reading job information from SLURM_RESUME_FILE.
  • Make aws-parallelcluster-node daemons handle only ParallelCluster-managed Slurm partitions.

BUG FIXES

  • Fix an issue that was causing misalignment of compute nodes DNS name on instances with multiple network interfaces,
    when using SlurmSettings/Dns/UseEc2Hostnames equals to True.

AWS ParallelCluster v3.6.1

05 Jul 14:22
e52e25b
Compare
Choose a tag to compare

We're excited to announce the release of AWS ParallelCluster Node 3.6.1

This is associated with AWS ParallelCluster v3.6.1

CHANGES

  • Avoid duplication of nodes seen by ClusterManager if compute nodes are added to multiple Slurm partitions.

BUG FIXES

  • Fix fast insufficient capacity fail-over logic when using Multiple Instance Types and no instances are returned.

AWS ParallelCluster v3.6.0

22 May 15:51
Compare
Choose a tag to compare

We're excited to announce the release of AWS ParallelCluster Node 3.6.0

This is associated with AWS ParallelCluster v3.6.0

CHANGES

  • Consider dynamic nodes failing Slurm registration, identified by INVALID_REG flag, as bootstrap failure towards the Slurm protected mode.
    Static nodes failing the Slurm registration are already treated as a bootstrap failure after the node_replacement_timeout.

BUG FIXES

  • Fix an issue that was causing misalignment of compute nodes IP on instances with multiple network interfaces.

AWS ParallelCluster v3.5.1

28 Mar 20:13
Compare
Choose a tag to compare

We're excited to announce the release of AWS ParallelCluster Node 3.5.1

This is associated with AWS ParallelCluster v3.5.1

BUG FIXES

  • Fix for compute_console_output log file being truncated at every clustermgtd iteration.

AWS ParallelCluster v3.5.0

20 Feb 11:50
Compare
Choose a tag to compare

We're excited to announce the release of AWS ParallelCluster Node 3.5.0

This is associated with AWS ParallelCluster v3.5.0

ENHANCEMENTS

  • Add logging of compute node console output to CloudWatch from head node on compute node bootstrap failure.
  • Add validators to prevent malicious string injection while calling the subprocess module.

BUG FIXES

  • Fix an issue in clustermgtd that caused compute nodes rebooted via Slurm to be replaced if the EC2 instance status checks fail.

AWS ParallelCluster v3.4.1

13 Jan 07:39
Compare
Choose a tag to compare

We're excited to announce the release of AWS ParallelCluster Node 3.4.1

This is associated with AWS ParallelCluster v3.4.1

CHANGES

  • There were no changes for this version.

AWS ParallelCluster v3.4.0

22 Dec 14:10
Compare
Choose a tag to compare

We're excited to announce the release of AWS ParallelCluster Node 3.4.0

This is associated with AWS ParallelCluster v3.4.0

ENHANCEMENTS

  • Add support for launching nodes across multiple availability zones to increase capacity availability.

CHANGES

  • Do not consider dynamic nodes in IDLE+CLOUD+COMPLETING+POWER_DOWN+NOT_RESPONDING as unhealthy anymore.
    • The root cause has been fixed in Slurm 22.05.6.

AWS ParallelCluster v3.3.1

03 Dec 00:49
Compare
Choose a tag to compare

We're excited to announce the release of AWS ParallelCluster Node 3.3.1

This is associated with AWS ParallelCluster v3.3.1

CHANGES

  • There were no changes for this version.