You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .github/PULL_REQUEST_TEMPLATE.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -63,7 +63,7 @@ This change added tests and can be verified as follows:
63
63
- The public API, i.e., is any changed class annotated with `@Public(Evolving)`: (yes / no)
64
64
- The serializers: (yes / no / don't know)
65
65
- The runtime per-record code paths (performance sensitive): (yes / no / don't know)
66
-
- Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: (yes / no / don't know)
66
+
- Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
67
67
- The S3 file system connector: (yes / no / don't know)
Copy file name to clipboardExpand all lines: docs/content.zh/docs/deployment/config.md
+6-19
Original file line number
Diff line number
Diff line change
@@ -46,7 +46,7 @@ The options in this section are the ones most commonly needed for a basic distri
46
46
47
47
These options are only necessary for *standalone* application- or session deployments ([simple standalone]({{< ref "docs/deployment/resource-providers/standalone/overview" >}}) or [Kubernetes]({{< ref "docs/deployment/resource-providers/standalone/kubernetes" >}})).
48
48
49
-
If you use Flink with [Yarn]({{< ref "docs/deployment/resource-providers/yarn" >}}), [Mesos]({{< ref "docs/deployment/resource-providers/mesos" >}}), or the [*active* Kubernetes integration]({{< ref "docs/deployment/resource-providers/native_kubernetes" >}}), the hostnames and ports are automatically discovered.
49
+
If you use Flink with [Yarn]({{< ref "docs/deployment/resource-providers/yarn" >}}) or the [*active* Kubernetes integration]({{< ref "docs/deployment/resource-providers/native_kubernetes" >}}), the hostnames and ports are automatically discovered.
50
50
51
51
-`rest.address`, `rest.port`: These are used by the client to connect to Flink. Set this to the hostname where the JobManager runs, or to the hostname of the (Kubernetes) service in front of the JobManager's REST interface.
52
52
@@ -95,7 +95,7 @@ You can configure checkpointing directly in code within your Flink job or applic
95
95
96
96
This data is NOT relied upon for persistence/recovery, but if this data gets deleted, it typically causes a heavyweight recovery operation. It is hence recommended to set this to a directory that is not automatically periodically purged.
97
97
98
-
Yarn, Mesos, and Kubernetes setups automatically configure this value to the local working directories by default.
98
+
Yarn and Kubernetes setups automatically configure this value to the local working directories by default.
99
99
100
100
----
101
101
----
@@ -112,7 +112,7 @@ The JobManager hostname and port are only relevant for standalone setups without
112
112
In that setup, the config values are used by the TaskManagers to find (and connect to) the JobManager.
113
113
In all highly-available setups, the TaskManagers discover the JobManager via the High-Availability-Service (for example ZooKeeper).
114
114
115
-
Setups using resource orchestration frameworks (K8s, Yarn, Mesos) typically use the framework's service discovery facilities.
115
+
Setups using resource orchestration frameworks (K8s, Yarn) typically use the framework's service discovery facilities.
116
116
117
117
You do not need to configure any TaskManager hosts and ports, unless the setup requires the use of specific port ranges or specific network interfaces to bind to.
118
118
@@ -206,7 +206,7 @@ Please refer to the [Flink and Kerberos Docs]({{< ref "docs/deployment/security/
206
206
207
207
# Resource Orchestration Frameworks
208
208
209
-
This section contains options related to integrating Flink with resource orchestration frameworks, like Kubernetes, Yarn, Mesos, etc.
209
+
This section contains options related to integrating Flink with resource orchestration frameworks, like Kubernetes, Yarn, etc.
210
210
211
211
Note that is not always necessary to integrate Flink with the resource orchestration framework.
212
212
For example, you can easily deploy Flink applications on Kubernetes without Flink knowing that it runs on Kubernetes (and without specifying any of the Kubernetes config options here.) See [this setup guide]({{< ref "docs/deployment/resource-providers/standalone/kubernetes" >}}) for an example.
@@ -221,19 +221,6 @@ The options in this section are necessary for setups where Flink itself actively
221
221
222
222
{{< generated/kubernetes_config_configuration >}}
223
223
224
-
### Mesos
225
-
226
-
{{< hint warning >}}
227
-
Apache Mesos support was deprecated in Flink 1.13 and is subject to removal in the future (see
228
-
[FLINK-22352](https://issues.apache.org/jira/browse/FLINK-22352) for further details).
@@ -413,7 +400,7 @@ The Blob Server is a component in the JobManager. It is used for distribution of
413
400
414
401
**ResourceManager**
415
402
416
-
These configuration keys control basic Resource Manager behavior, independent of the used resource orchestration management framework (YARN, Mesos, etc.)
403
+
These configuration keys control basic Resource Manager behavior, independent of the used resource orchestration management framework (YARN, etc.)
417
404
418
405
{{< generated/resource_manager_configuration >}}
419
406
@@ -443,7 +430,7 @@ Flink does not use Akka for data transport.
443
430
444
431
# Forwarding Environment Variables
445
432
446
-
You can configure environment variables to be set on the JobManager and TaskManager processes started on Yarn/Mesos.
433
+
You can configure environment variables to be set on the JobManager and TaskManager processes started on Yarn.
447
434
448
435
-`containerized.master.env.`: Prefix for passing custom environment variables to Flink's JobManager process.
449
436
For example for passing LD_LIBRARY_PATH as an env variable to the JobManager, set containerized.master.env.LD_LIBRARY_PATH: "/usr/lib/native"
Copy file name to clipboardExpand all lines: docs/content.zh/docs/deployment/elastic_scaling.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -113,7 +113,7 @@ Additionally, one can configure [`jobmanager.adaptive-scheduler.min-parallelism-
113
113
114
114
Since Reactive Mode is a new, experimental feature, not all features supported by the default scheduler are also available with Reactive Mode (and its adaptive scheduler). The Flink community is working on addressing these limitations.
115
115
116
-
-**Deployment is only supported as a standalone application deployment**. Active resource providers (such as native Kubernetes, YARN or Mesos) are explicitly not supported. Standalone session clusters are not supported either. The application deployment is limited to single job applications.
116
+
-**Deployment is only supported as a standalone application deployment**. Active resource providers (such as native Kubernetes, YARN) are explicitly not supported. Standalone session clusters are not supported either. The application deployment is limited to single job applications.
117
117
118
118
The only supported deployment options are [Standalone in Application Mode]({{< ref "docs/deployment/resource-providers/standalone/overview" >}}#application-mode) ([described](#getting-started) on this page), [Docker in Application Mode]({{< ref "docs/deployment/resource-providers/standalone/docker" >}}#application-mode-on-docker) and [Standalone Kubernetes Application Cluster]({{< ref "docs/deployment/resource-providers/standalone/kubernetes" >}}#deploy-application-cluster).
0 commit comments