batch_delete_cluster_nodes
async
¶
batch_delete_cluster_nodes(
*,
config_overrides: Optional[AsyncSageMakerClientConfig] = None,
cluster_name: Optional[ClusterNameOrArn] = None,
node_ids: Optional[ClusterNodeIds] = None,
node_logical_ids: Optional[ClusterNodeLogicalIdList] = None,
) -> BatchDeleteClusterNodesResponse
Deletes specific nodes within a SageMaker HyperPod cluster. BatchDeleteClusterNodes accepts a cluster name and a list of node IDs.
-
To safeguard your work, back up your data to Amazon S3 or an FSx for Lustre file system before invoking the API on a worker node group. This will help prevent any potential data loss from the instance root volume. For more information about backup, see Use the backup script provided by SageMaker HyperPod.
-
If you want to invoke this API on an existing cluster, you'll first need to patch the cluster by running the UpdateClusterSoftware API. For more information about patching a cluster, see Update the SageMaker HyperPod platform software of a cluster.
Parameters:
-
cluster_name(Optional[ClusterNameOrArn], default:None) –The name of the SageMaker HyperPod cluster from which to delete the specified nodes.
-
node_ids(Optional[ClusterNodeIds], default:None) –A list of node IDs to be deleted from the specified cluster.
-
For SageMaker HyperPod clusters using the Slurm workload manager, you cannot remove instances that are configured as Slurm controller nodes.
-
If you need to delete more than 99 instances, contact Support for assistance.
-
-
node_logical_ids(Optional[ClusterNodeLogicalIdList], default:None) –A list of
NodeLogicalIdsidentifying the nodes to be deleted. You can specify up to 50NodeLogicalIds. You must specify eitherNodeLogicalIds,InstanceIds, or both, with a combined maximum of 50 identifiers.
Raises:
-
ResourceNotFound–Resource being access is not found.
-
UnknownServiceError–The service returned an error code this client does not model.