Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
Yandex Data Processing
  • Getting started
  • Access management
  • Pricing policy
  • Terraform reference
    • Authentication with the API
      • Overview
        • Overview
        • Get
        • List
        • Create
        • Update
        • Delete
        • Start
        • Stop
        • ListOperations
        • ListHosts
        • ListUILinks
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • FAQ

In this article:

  • gRPC request
  • ListClusterHostsRequest
  • ListClusterHostsResponse
  • Host
  1. API reference
  2. gRPC
  3. Cluster
  4. ListHosts

Yandex Data Processing API, gRPC: ClusterService.ListHosts

Written by
Yandex Cloud
Updated at April 2, 2025
  • gRPC request
  • ListClusterHostsRequest
  • ListClusterHostsResponse
  • Host

Retrieves the list of hosts in the specified cluster.

gRPC requestgRPC request

rpc ListHosts (ListClusterHostsRequest) returns (ListClusterHostsResponse)

ListClusterHostsRequestListClusterHostsRequest

{
  "cluster_id": "string",
  "page_size": "int64",
  "page_token": "string",
  "filter": "string"
}

Field

Description

cluster_id

string

ID of the cluster to list hosts for.

To get a cluster ID, make a ClusterService.List request.

page_size

int64

The maximum number of results per page to return. If the number of available
results is larger than page_size, the service returns a ListClusterHostsResponse.next_page_token
that can be used to get the next page of results in subsequent list requests.
Default value: 100.

page_token

string

Page token. To get the next page of results, set page_token to the
ListClusterHostsResponse.next_page_token returned by a previous list request.

filter

string

A filter expression that filters hosts listed in the response.

The expression must specify:

  1. The field name. Currently you can use filtering only on Cluster.name field.
  2. An = operator.
  3. The value in double quotes ("). Must be 3-63 characters long and match the regular expression [a-z][-a-z0-9]{1,61}[a-z0-9].
    Example of a filter: name=my-host

ListClusterHostsResponseListClusterHostsResponse

{
  "hosts": [
    {
      "name": "string",
      "subcluster_id": "string",
      "health": "Health",
      "compute_instance_id": "string",
      "role": "Role"
    }
  ],
  "next_page_token": "string"
}

Field

Description

hosts[]

Host

Requested list of hosts.

next_page_token

string

Token for getting the next page of the list. If the number of results is greater than
the specified ListClusterHostsRequest.page_size, use next_page_token as the value
for the ListClusterHostsRequest.page_token parameter in the next list request.

Each subsequent page will have its own next_page_token to continue paging through the results.

HostHost

A Yandex Data Processing host. For details about the concept, see documentation.

Field

Description

name

string

Name of the Yandex Data Processing host. The host name is assigned by Yandex Data Processing at creation time
and cannot be changed. The name is generated to be unique across all Yandex Data Processing
hosts that exist on the platform, as it defines the FQDN of the host.

subcluster_id

string

ID of the Yandex Data Processing subcluster that the host belongs to.

health

enum Health

Status code of the aggregated health of the host.

  • HEALTH_UNKNOWN: Object is in unknown state (we have no data).
  • ALIVE: Object is alive and well (for example, all hosts of the cluster are alive).
  • DEAD: Object is inoperable (it cannot perform any of its essential functions).
  • DEGRADED: Object is partially alive (it can perform some of its essential functions).

compute_instance_id

string

ID of the Compute virtual machine that is used as the Yandex Data Processing host.

role

enum Role

Role of the host in the cluster.

  • ROLE_UNSPECIFIED

  • MASTERNODE: The subcluster fulfills the master role.

    Master can run the following services, depending on the requested components:

  • HDFS: Namenode, Secondary Namenode
  • YARN: ResourceManager, Timeline Server
  • HBase Master
  • Hive: Server, Metastore, HCatalog
  • Spark History Server
  • Zeppelin
  • ZooKeeper
  • DATANODE: The subcluster is a DATANODE in a Yandex Data Processing cluster.

    DATANODE can run the following services, depending on the requested components:

  • HDFS DataNode
  • YARN NodeManager
  • HBase RegionServer
  • Spark libraries
  • COMPUTENODE: The subcluster is a COMPUTENODE in a Yandex Data Processing cluster.

    COMPUTENODE can run the following services, depending on the requested components:

  • YARN NodeManager
  • Spark libraries

Was the article helpful?

Previous
ListOperations
Next
ListUILinks
© 2025 Direct Cursus Technology L.L.C.