> ## Documentation Index > Fetch the complete documentation index at: https://docs.nebius.com/llms.txt > Use this file to discover all available pages before exploring further. # Set Unhealthy > 1. Scheduler makes the best effort not to assign new VMs to the unhealthy node, but in case of no capacity, the VM can be assigned to an unhealthy node. 2. The existing VMs continue to work on the node, but after stop/start via Compute API they most probably will be assigned to a different node. To use this rpc one needs to obtain `compute.node.setUnhealthy` permission for the VM's parent container. The permission is granted to the TSA inside the VM. ## OpenAPI ````yaml https://api.nebius.cloud/openapi.json post /compute/v1/nodes/set-unhealthy openapi: 3.0.3 info: title: Nebius API version: version not set servers: - url: https://api.nebius.cloud security: - bearerAuth: [] tags: - name: nebius.ai.v1.EndpointService - name: nebius.ai.v1.JobService - name: nebius.applications.v1alpha1.K8sReleaseService - name: nebius.audit.v2.AuditEventExportService - name: nebius.audit.v2.AuditEventService - name: nebius.billing.v1.CalculatorService - name: nebius.billing.v1alpha1.CalculatorService - name: nebius.billing.v1alpha1.OneTimeExportService - name: nebius.capacity.v1.CapacityAllowanceService - name: nebius.capacity.v1.CapacityBlockGroupService - name: nebius.capacity.v1.CapacityIntervalService - name: nebius.capacity.v1.ResourceAdviceService - name: nebius.compute.v1.DiskService - name: nebius.compute.v1.DiskSnapshotService - name: nebius.compute.v1.FilesystemService - name: nebius.compute.v1.GpuClusterService - name: nebius.compute.v1.ImageService - name: nebius.compute.v1.InstanceService - name: nebius.compute.v1.MaintenanceService - name: nebius.compute.v1.NVLInstanceGroupService - name: nebius.compute.v1.NodeService - name: nebius.compute.v1.PlatformService - name: nebius.dns.v1.RecordService - name: nebius.dns.v1.ZoneService - name: nebius.iam.v1.AccessKeyService - name: nebius.iam.v1.AccessPermitService - name: nebius.iam.v1.AuthPublicKeyService - name: nebius.iam.v1.FederatedCredentialsService - name: nebius.iam.v1.FederationCertificateService - name: nebius.iam.v1.FederationService - name: nebius.iam.v1.GroupMembershipService - name: nebius.iam.v1.GroupService - name: nebius.iam.v1.InvitationService - name: nebius.iam.v1.ProfileService - name: nebius.iam.v1.ProjectService - name: nebius.iam.v1.ServiceAccountService - name: nebius.iam.v1.SessionManagementService - name: nebius.iam.v1.StaticKeyService - name: nebius.iam.v1.TenantService - name: nebius.iam.v1.TenantUserAccountService - name: nebius.iam.v1.TenantUserAccountWithAttributesService - name: nebius.iam.v2.AccessKeyService - name: nebius.iam.v2.ProjectService - name: nebius.iam.v2.TenantService - name: nebius.kms.v1.AsymmetricCryptoService - name: nebius.kms.v1.AsymmetricKeyService - name: nebius.kms.v1.SymmetricCryptoService - name: nebius.kms.v1.SymmetricKeyService - name: nebius.logging.agentmanager.v1.VersionService - name: nebius.logging.v1.LogExportService - name: nebius.maintenance.v1alpha1.MaintenanceService - name: nebius.mk8s.v1.ClusterService - name: nebius.mk8s.v1.NodeGroupService - name: nebius.mk8s.v1alpha1.ClusterService - name: nebius.mk8s.v1alpha1.NodeGroupService - name: nebius.msp.mlflow.v1alpha1.ClusterService - name: nebius.msp.postgresql.v1alpha1.BackupService - name: nebius.msp.postgresql.v1alpha1.ClusterService - name: nebius.mysterybox.v1.PayloadService - name: nebius.mysterybox.v1.SecretService - name: nebius.mysterybox.v1.SecretVersionService - name: nebius.quotas.v1.QuotaAllowanceService - name: nebius.registry.v1.ArtifactService - name: nebius.registry.v1.RegistryService - name: nebius.storage.v1.BucketService - name: nebius.storage.v1.TransferService - name: nebius.storage.v1alpha1.TransferService - name: nebius.tunnel.v1.TunnelService - name: nebius.vpc.v1.AllocationService - name: nebius.vpc.v1.NetworkService - name: nebius.vpc.v1.PoolService - name: nebius.vpc.v1.RouteService - name: nebius.vpc.v1.RouteTableService - name: nebius.vpc.v1.SecurityGroupService - name: nebius.vpc.v1.SecurityRuleService - name: nebius.vpc.v1.SubnetService - name: nebius.vpc.v1.TargetGroupService - name: nebius.vpc.v1alpha1.AllocationService - name: nebius.vpc.v1alpha1.NetworkService - name: nebius.vpc.v1alpha1.PoolService - name: nebius.vpc.v1alpha1.ScopeService - name: nebius.vpc.v1alpha1.SubnetService paths: /compute/v1/nodes/set-unhealthy: post: tags: - nebius.compute.v1.NodeService summary: Set Unhealthy description: >- 1. Scheduler makes the best effort not to assign new VMs to the unhealthy node, but in case of no capacity, the VM can be assigned to an unhealthy node. 2. The existing VMs continue to work on the node, but after stop/start via Compute API they most probably will be assigned to a different node. To use this rpc one needs to obtain `compute.node.setUnhealthy` permission for the VM's parent container. The permission is granted to the TSA inside the VM. operationId: NodeService_SetUnhealthy requestBody: content: application/json: schema: $ref: '#/components/schemas/v1NodeSetUnhealthyRequest' required: true x-originalParamName: body responses: '200': content: application/json: schema: $ref: '#/components/schemas/v1NodeSetUnhealthyResponse' description: A successful response. components: schemas: v1NodeSetUnhealthyRequest: properties: dryRun: title: >- If set to true, the call performs the authorization and limit checks, but does not mark node unhealthy. False by default type: boolean healthCheckInfo: $ref: '#/components/schemas/NodeSetUnhealthyRequestHealthCheckInfo' instanceId: type: string required: - instanceId - healthCheckInfo type: object v1NodeSetUnhealthyResponse: type: object NodeSetUnhealthyRequestHealthCheckInfo: properties: checkId: title: >- Identifies specific GPU check that failed in soperator (key for observability) type: string description: title: Human-readable description of the error for further investigation type: string observedAt: format: date-time title: Time when the unhealthy node was observed type: string required: - observedAt - checkId - description type: object securitySchemes: bearerAuth: description: The Authorization header expects a Bearer token. scheme: bearer type: http ````