Section | Parameter | Description |
Standard | Name | The name of the session cluster that you want to create. |
Deployment Target | The queue in which the draft is deployed. For more information about how to create a queue, see Manage queues. |
State | The desired state of the cluster. Valid values: RUNNING: The cluster keeps running after it is configured. STOPPED: The cluster is stopped after it is configured, and the deployments that are deployed in the cluster are also stopped.
|
Label key | You can configure labels for deployments in the Labels section. This allows you to find a deployment on the Overview page in an efficient manner. |
Label value | N/A |
Configuration | Engine Version | The version of the Flink engine that is used by the current deployment. For more information about engine versions, see Engine version and Lifecycle policies. We recommend that you use a recommended version or a stable version. Engine versions are classified into the following types: Recommended: the latest minor version of the latest major version. Stable: the latest minor version of a major version that is still in the service period of the product. Defects in previous versions are fixed in such a version. Normal: other minor versions that are still in the service period of the product. Deprecated: the version that exceeds the service period of the product.
|
Flink Restart Policy | Valid values: Failure Rate: The JobManager is restarted if the number of failures within the specified interval exceeds the upper limit. If you select this option, you must configure the Failure Rate Interval, Max failures per interval, and Delay Between Restart Attempts parameters. Fixed Delay: The JobManager is restarted at a fixed interval. If you select this option, you must configure the Number of Restart Attempts and Delay Between Restart Attempts parameters. No Restarts: The JobManager is not restarted if tasks fail.
Important If you leave this parameter empty, the default Apache Flink restart policy is used. In this case, if a task fails and checkpointing is disabled, the JobManager is not restarted. If you enable checkpointing, the JobManager is restarted. |
Other Configuration | Configure other Flink settings, such as taskmanager.numberOfTaskSlots: 1 . |
Resources | Number of TaskManagers | By default, the value is the same as the parallelism. |
JobManager CPU Cores | Default value: 1. |
JobManager Memory | Minimum value: 1 GiB. Recommended value: 4 GiB. JobManager memory can also be measured in MiB. For example, you can set this parameter to 1024 MiB or 1.5 GiB. |
TaskManager CPU Cores | Default value: 2. |
TaskManager Memory | Minimum value: 1 GiB. Recommended value: 8 GiB. TaskManager memory can also be measured in MiB. For example, you can set this parameter to 1024 MiB or 1.5 GiB. We recommend that you specify the number of slots for each TaskManager and the amount of resources that are available for TaskManagers. The number of slots is specified by the taskmanager.numberOfTaskSlots parameter. When you configure this parameter, take note of the following points: For a single small deployment, we recommend that you set the CPU-to-memory ratio of a single slot to 1:4 and configure at least 1 CPU core and 2 GiB of memory for each slot. For a complex deployment, we recommend that you configure at least 1 CPU core and 4 GiB of memory for each slot. If you use the default resource configuration, you can configure two slots for each TaskManager. We recommend that you use the default resource configuration for each TaskManager and set the number of slots to 2. Important Insufficient TaskManager resources affect the stability of the deployments that run on the TaskManager. Additionally, configuring only a small number of slots underutilizes resources because the overhead of the TaskManager cannot be effectively spread across tasks. Configuring a large number of resources for a TaskManager means a large number of deployments run on the TaskManager. If the TaskManager is faulty, all the deployments will be affected.
|
Logging | Root Log Level | The following log levels are supported and listed in ascending order of importance. TRACE: records finer-grained information than DEBUG logs. DEBUG: records the status of the system. INFO: records important system information. WARN: records the information about potential errors. ERROR: records the information about errors and exceptions that occur.
|
Log Levels | The name and level of the log. |
Logging Profile | The log template. You can choose a default or custom profile template. |