Aws-parallelcluster-node

Latest version: v3.12.0

Safety actively analyzes 693883 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 8 of 11

2.8.1

Not secure
-----

**CHANGES**
- There were no notable changes for this version.

2.8.0

Not secure
-----

**ENHANCEMENTS**
- Dynamically generate the architecture-specific portion of the path to the SGE binaries directory.

2.7.0

Not secure
-----

**ENHANCEMENTS**
- `sqswatcher`: The daemon is now compatible with VPC Endpoints so that SQS messages can be passed without traversing
the public internet.

2.6.1

Not secure
-----

**ENHANCEMENTS**
- Improved the management of SQS messages and retries to speed-up recovery times when failures occur.

**CHANGES**
- Do not launch a replacement for an unhealthy or unresponsive node until this is terminated. This makes cluster slower
at provisioning new nodes when failures occur but prevents any temporary over-scaling with respect to the expected
capacity.
- Increase parallelism when starting `slurmd` on compute nodes that join the cluster from 10 to 30.
- Reduce the verbosity of messages logged by the node daemons.
- Do not dump logs to `/home/logs` when nodewatcher encounters a failure and terminates the node. CloudWatch can be
used to debug such failures.
- Reduce the number of retries for failed REMOVE events in sqswatcher.

**BUG FIXES**
- Fixed a bug in the ordering and retrying of SQS messages that was causing, under certain circumstances of heavy load,
the scheduler configuration to be left in an inconsistent state.
- Delete from queue the REMOVE events that are discarded due to hostname collision with another event fetched as part
of the same `sqswatcher` iteration.

2.6.0

Not secure
-----

**CHANGES**
- Remove logic that was adding compute nodes identity to known_hosts file for all OSs except CentOS6

**BUG FIXES**
- Fix Torque issue that was limiting the max number of running jobs to the max size of the cluster.

2.5.1

Not secure
-----

**BUG FIXES**
- Fix bug in sqswatcher that was causing the daemon to crash when more than 100 DynamoDB tables are present in the
cluster region.

Page 8 of 11

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.