Class NodeService

constructor

• new NodeService(sdk: SDKInterface): NodeService

  Creates a client that uses the SDK service address.

  Parameters

  • sdk: SDKInterface

  Returns NodeService

$type

setUnhealthy

• setUnhealthy(
      request: NodeSetUnhealthyRequest,
  ): Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

  SetUnhealthy marks the node underlying the Compute VM as unhealthy, which has the following effect:

  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.

  Parameters

  • request: NodeSetUnhealthyRequest

  Returns Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

• setUnhealthy(
      request: NodeSetUnhealthyRequest,
      metadata: Metadata,
  ): Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

  SetUnhealthy marks the node underlying the Compute VM as unhealthy, which has the following effect:

  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.

  Parameters

  • request: NodeSetUnhealthyRequest
  • metadata: Metadata

  Returns Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

• setUnhealthy(
      request: NodeSetUnhealthyRequest,
      metadata: Metadata,
      options: Partial<CallOptions> & RetryOptions,
  ): Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

  SetUnhealthy marks the node underlying the Compute VM as unhealthy, which has the following effect:

  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.

  Parameters

  • request: NodeSetUnhealthyRequest
  • metadata: Metadata
  • options: Partial<CallOptions> & RetryOptions

  Returns Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

• setUnhealthy(
      request: NodeSetUnhealthyRequest,
  ): Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

  SetUnhealthy marks the node underlying the Compute VM as unhealthy, which has the following effect:

  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.

  Parameters

  • request: NodeSetUnhealthyRequest

  Returns Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

• setUnhealthy(
      request: NodeSetUnhealthyRequest,
      metadata: Metadata,
  ): Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

  SetUnhealthy marks the node underlying the Compute VM as unhealthy, which has the following effect:

  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.

  Parameters

  • request: NodeSetUnhealthyRequest
  • metadata: Metadata

  Returns Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

• setUnhealthy(
      request: NodeSetUnhealthyRequest,
      metadata: Metadata,
      options: Partial<CallOptions> & RetryOptions,
  ): Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>

  SetUnhealthy marks the node underlying the Compute VM as unhealthy, which has the following effect:

  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.

  Parameters

  • request: NodeSetUnhealthyRequest
  • metadata: Metadata
  • options: Partial<CallOptions> & RetryOptions

  Returns Request<NodeSetUnhealthyRequest, NodeSetUnhealthyResponse>