Stopping and starting an Apache Airflow™ cluster
You can stop and restart an Apache Airflow™ cluster as needed. When stopped, a cluster retains all its data. The data will be available again as soon as you restart the cluster.
Stopping a cluster
- In the management console
, go to the relevant folder. - In the list of services, select Managed Service for Apache Airflow™.
- Find the cluster you need in the list, click
, and select Stop. - In the dialog box that opens, confirm that you want to stop the cluster and click Stop.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
To stop a cluster, run the command:
yc managed-airflow cluster stop <cluster_name_or_ID>
-
Get an IAM token for API authentication and put it into the environment variable:
export IAM_TOKEN="<IAM_token>"
-
Use the Cluster.stop method to make a request, e.g., via cURL
:curl \ --request POST \ --header "Authorization: Bearer $IAM_TOKEN" \ --url 'https://airflow.api.cloud.yandex.net/managed-airflow/v1/clusters/<cluster_ID>:stop'
You can get the cluster ID with a list of clusters in the folder.
-
View the server response to make sure the request was successful.
-
Get an IAM token for API authentication and put it into the environment variable:
export IAM_TOKEN="<IAM_token>"
-
Clone the cloudapi
repository:cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
Below, we assume the repository contents are stored in the
~/cloudapi/
directory. -
Use the ClusterService/Stop call to make a request, e.g., via gRPCurl
:grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/airflow/v1/cluster_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "cluster_id": "<cluster_ID>" }' \ airflow.api.cloud.yandex.net:443 \ yandex.cloud.airflow.v1.ClusterService.Stop
You can get the cluster ID with a list of clusters in the folder.
-
View the server response to make sure the request was successful.
Starting a cluster
You can restart clusters with the Stopped
status.
- In the management console
, go to the relevant folder. - In the list of services, select Managed Service for Apache Airflow™.
- Find the stopped cluster you need in the list, click
, and select Start. - In the window that opens, click Start.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
To start a cluster, run the command:
yc managed-airflow cluster start <cluster_name_or_ID>
-
Get an IAM token for API authentication and put it into the environment variable:
export IAM_TOKEN="<IAM_token>"
-
Use the Cluster.start method to make a request, e.g., via cURL
:curl \ --request POST \ --header "Authorization: Bearer $IAM_TOKEN" \ --url 'https://airflow.api.cloud.yandex.net/managed-airflow/v1/clusters/<cluster_ID>:start'
You can get the cluster ID with a list of clusters in the folder.
-
View the server response to make sure the request was successful.
-
Get an IAM token for API authentication and put it into the environment variable:
export IAM_TOKEN="<IAM_token>"
-
Clone the cloudapi
repository:cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapi
Below, we assume the repository contents are stored in the
~/cloudapi/
directory. -
Use the ClusterService/Start call to make a request, e.g., via gRPCurl
:grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/airflow/v1/cluster_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "cluster_id": "<cluster_ID>" }' \ airflow.api.cloud.yandex.net:443 \ yandex.cloud.airflow.v1.ClusterService.Start
You can get the cluster ID with a list of clusters in the folder.
-
View the server response to make sure the request was successful.