Viewing operations with clusters
All actions with Yandex MPP Analytics for PostgreSQL clusters are logged as a list of operations. Each operation gets its own unique ID.
Getting a list of operations
-
In the management console
, open the folder containing the cluster. -
Navigate to Yandex MPP Analytics for PostgreSQL.
-
In the left-hand panel, select
Clusters. -
Select the cluster and open the
Operations tab.You will see the list of operations with the cluster.
If you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.
To get a list of operations for a Yandex MPP Analytics for PostgreSQL cluster, run this command:
yc managed-greenplum cluster list-operations <cluster_name_or_ID>
Result:
+----------------------+---------------------+----------------------+---------------------+--------+--------------------------+
| ID | CREATED AT | CREATED BY | MODIFIED AT | STATUS | DESCRIPTION |
+----------------------+---------------------+----------------------+---------------------+--------+--------------------------+
| dqh0ntf6batm******** | 2024-09-07 16:36:46 | aje9k8luj4qf******** | 2024-09-07 16:44:12 | DONE | Create Greenplum cluster |
+----------------------+---------------------+----------------------+---------------------+--------+--------------------------+
You can get the cluster ID and name with the list of clusters in the folder.
By default, information about operations is output as text. To get more details, specify the yaml or json output data format using --format:
yc managed-greenplum cluster list-operations c9qk2926qqu9******** --format yaml
Result:
- id: dqh0ntf6batm********
description: Create Greenplum cluster
created_at: "2024-09-07T16:36:46.816682Z"
created_by: aje9k8luj4qf********
modified_at: "2024-09-07T16:44:12.944302Z"
done: true
metadata:
'@type': type.googleapis.com/yandex.cloud.mdb.greenplum.v1.CreateClusterMetadata
cluster_id: c9q13q0acgv7********
response:
'@type': type.googleapis.com/google.rpc.Status
message: OK
-
Get an IAM token for API authentication and put it into an environment variable:
export IAM_TOKEN="<IAM_token>" -
Call the Cluster.ListOperations method, e.g., via the following cURL
request:curl \ --request GET \ --header "Authorization: Bearer $IAM_TOKEN" \ --url 'https://mdb.api.cloud.yandex.net/managed-greenplum/v1/clusters/<cluster_ID>/operations'You can request the cluster ID with the list of clusters in the folder.
-
Check the server response to make sure your request was successful.
-
Get an IAM token for API authentication and put it into an environment variable:
export IAM_TOKEN="<IAM_token>" -
Clone the cloudapi
repository:cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapiBelow, we assume that the repository contents reside in the
~/cloudapi/directory. -
Call the ClusterService.ListOperations method, e.g., via the following gRPCurl
request:grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/mdb/greenplum/v1/cluster_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "cluster_id": "<cluster_ID>" }' \ mdb.api.cloud.yandex.net:443 \ yandex.cloud.mdb.greenplum.v1.ClusterService.ListOperationsYou can request the cluster ID with the list of clusters in the folder.
-
Check the server response to make sure your request was successful.
Getting operation details
-
Get the list of operations for the cluster.
-
Copy the ID of the operation you need.
-
Get the operation details:
CLIREST APIgRPC APIIf you do not have the Yandex Cloud CLI yet, install and initialize it.
The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the
yc config set folder-id <folder_ID>command. You can also specify a different folder for any command using--folder-nameor--folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.Run this command:
yc operation get <operation_ID>Result:
id: dqh0ntf6batm******** description: Create Greenplum cluster created_at: "2024-09-07T16:36:46.816682Z" created_by: aje9k8luj4qf******** modified_at: "2024-09-07T16:44:12.944302Z" done: true metadata: '@type': type.googleapis.com/yandex.cloud.mdb.greenplum.v1.CreateClusterMetadata cluster_id: c9q13q0acgv7******** response: '@type': type.googleapis.com/yandex.cloud.mdb.greenplum.v1.Cluster ...-
Get an IAM token for API authentication and put it into an environment variable:
export IAM_TOKEN="<IAM_token>" -
Call the Operation.Get method, e.g., via the following cURL
request:curl \ --request GET \ --header "Authorization: Bearer $IAM_TOKEN" \ --url 'https://operation.api.cloud.yandex.net/operations/<operation_ID>' -
Check the server response to make sure your request was successful.
-
Get an IAM token for API authentication and put it into an environment variable:
export IAM_TOKEN="<IAM_token>" -
Clone the cloudapi
repository:cd ~/ && git clone --depth=1 https://github.com/yandex-cloud/cloudapiBelow, we assume that the repository contents reside in the
~/cloudapi/directory. -
Call the OperationService.Get method, e.g., via the following gRPCurl
request:grpcurl \ -format json \ -import-path ~/cloudapi/ \ -import-path ~/cloudapi/third_party/googleapis/ \ -proto ~/cloudapi/yandex/cloud/operation/operation_service.proto \ -rpc-header "Authorization: Bearer $IAM_TOKEN" \ -d '{ "operation_id": "<operation_ID>" }' \ operation.api.cloud.yandex.net:443 \ yandex.cloud.operation.OperationService.Get -
Check the server response to make sure your request was successful.
-
See also
Greenplum® and Greenplum Database® are registered trademarks or trademarks of Broadcom Inc. in the United States and/or other countries.