yc managed-greenplum cluster update
Update the specified Greenplum cluster
Command Usage
Syntax:
yc managed-greenplum cluster update <CLUSTER-NAME>|<CLUSTER-ID> [Flags...] [Global Flags...]
Flags
|
Flag |
Description |
|
|
Greenplum cluster id. |
|
|
Greenplum cluster name. |
|
|
Display information about the operation in progress, without waiting for the operation to complete. |
|
|
Cluster description. |
|
|
A list of label KEY=VALUE pairs to add. |
|
|
New name for the Greenplum cluster |
|
|
Deletion Protection inhibits deletion of the cluster. |
|
|
Owner user password. Must be 8-128 characters long. |
|
|
A list of security groups for the Greenplum cluster. |
|
|
Descriptions of master config resources for Greenplum cluster. Possible property names:
|
|
|
Descriptions of segment config resources for Greenplum cluster. Possible property names:
|
|
|
Network id. |
|
|
Network name. |
|
|
Descriptions of cloud storage for Greenplum cluster. Possible property names:
|
|
|
ID of the service account used for access Yandex Cloud resources. |
|
|
Maintenance window settings Possible property names:
|
|
|
Allow access for DataLens. |
|
|
Allow access for Web SQL. |
|
|
Allow access for DataTransfer. |
|
|
Allow access for Yandex Query. |
|
|
Start time for the daily backup in UTC timezone. Format: HH:MM:SS |
|
|
Retention time in days of automated backups |
|
|
Whether the host should get a public IP address. |
|
|
Connection pooler pooling mode Values: 'session', 'transaction' |
|
|
Connection pooler size |
|
|
Connection pooler client idle timeout |
|
|
Connection pooler idle in transaction timeout |
|
|
Timeout for pxf connections |
|
|
Timeout for uploading pxf connections |
|
|
The maximum number of PXF tomcat threads. |
|
|
Identifies whether or not core streaming threads are allowed to time out. |
|
|
The number of core streaming threads. |
|
|
The capacity of the core streaming thread pool queue. |
|
|
The maximum allowed number of core streaming threads. |
|
|
Max jvm memory |
|
|
Starting jvm memory |
|
|
ANALYZE Possible property names:
|
|
|
Configuration of script that kills long running queries that are in idle state. Possible property names:
|
|
|
in transaction Possible property names:
|
|
|
Configuration of script that kills long running queries (in any state). Possible property names:
|
|
|
Whether logs generated by the Greenplum components are delivered to Cloud Logging. |
|
|
ID of the folder to store logs in default log_group. |
|
|
ID of the log_group to store logs in. |
|
|
Whether logs generated by the Command Center are delivered to Cloud Logging. |
|
|
Whether logs generated by the Greenplum are delivered to Cloud Logging. |
|
|
Whether logs generated by the Pooler are delivered to Cloud Logging. |
Global Flags
|
Flag |
Description |
|
|
Set the custom configuration file. |
|
|
Debug logging. |
|
|
Debug gRPC logging. Very verbose, used for debugging connection problems. |
|
|
Disable printing user intended output to stderr. |
|
|
Enable gRPC retries. By default, retries are enabled with maximum 5 attempts. |
|
|
Set the ID of the cloud to use. |
|
|
Set the ID of the folder to use. |
|
|
Set the name of the folder to use (will be resolved to id). |
|
|
Set the Cloud API endpoint (host:port). |
|
|
Set the OAuth token to use. |
|
|
Set the ID of the service account to impersonate. |
|
|
Disable opening browser for authentication. |
|
|
Set the output format: text (default), yaml, json, json-rest. |
|
|
Query to select values from the response using jq syntax |
|
|
Display help for the command. |