Set-HpcPool
Sets the weight of a resource pool.
Syntax
Set-HpcPool
-Pool <HpcPool>
[-Weight <Int32>]
[-Scheduler <String[]>]
[<CommonParameters>]
Set-HpcPool
-Name <String>
[-Weight <Int32>]
[-Scheduler <String[]>]
[<CommonParameters>]
Description
The Set-HpcPool cmdlet sets the weight of an HPC resource pool. This cmdlet returns an error if the specified pool does not exist, or if the specified weight is less than 0 or greater than 999,999.
Examples
Example 1: Set the weight of a resource pool
PS C:\>Set-HpcPool -Name "Pool01" -Weight 10
This command sets the weight of an existing pool using the pool name and weight parameters.
Parameters
-Name
Specifies the name of the resource pool that you will be setting the weight on. You cannot specify both the Name and the Pool parameters.
Type: | String |
Position: | Named |
Default value: | None |
Required: | True |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-Pool
Specifies the HpcPool object. You cannot specify both the Name and the Pool parameters.
Type: | HpcPool |
Position: | Named |
Default value: | None |
Required: | True |
Accept pipeline input: | True |
Accept wildcard characters: | False |
-Scheduler
Specifies the host name or IP address of the head node for the cluster that contains the resource pool. The value must be a valid computer name or IP address. If you do not specify the Scheduler parameter, this cmdlet uses the scheduler on the head node that the CCP_SCHEDULER environment variable specifies.
Type: | String[] |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
-Weight
Specifies the pool weight.
Type: | Int32 |
Position: | Named |
Default value: | None |
Required: | False |
Accept pipeline input: | False |
Accept wildcard characters: | False |
Notes
This cmdlet was introduced in HPC Pack 2008 R2 with Service Pack 2 (SP2). It is not supported in previous versions.
Related Links
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for