This is an automated email from the ASF dual-hosted git repository.
fanrui pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/flink.git
The following commit(s) were added to refs/heads/master by this push:
new d44e940e9d2 [FLINK-34247][doc] Fix the wrong zh link for
flink-configuration-file and repeated flink configuration file
d44e940e9d2 is described below
commit d44e940e9d28518115cf6e8d5ba4f963faf30f52
Author: Rui Fan <[email protected]>
AuthorDate: Mon Feb 5 13:21:34 2024 +0800
[FLINK-34247][doc] Fix the wrong zh link for flink-configuration-file and
repeated flink configuration file
---
docs/content.zh/docs/connectors/table/filesystem.md | 4 ++--
docs/content.zh/docs/deployment/advanced/historyserver.md | 2 +-
docs/content.zh/docs/deployment/cli.md | 4 ++--
docs/content.zh/docs/deployment/filesystems/azure.md | 6 +++---
docs/content.zh/docs/deployment/filesystems/gcs.md | 6 +++---
docs/content.zh/docs/deployment/filesystems/oss.md | 6 +++---
docs/content.zh/docs/deployment/filesystems/s3.md | 12 ++++++------
docs/content.zh/docs/deployment/ha/kubernetes_ha.md | 2 +-
docs/content.zh/docs/deployment/ha/zookeeper_ha.md | 4 ++--
docs/content.zh/docs/deployment/memory/mem_migration.md | 4 ++--
docs/content.zh/docs/deployment/metric_reporters.md | 2 +-
.../deployment/resource-providers/native_kubernetes.md | 4 ++--
.../deployment/resource-providers/standalone/docker.md | 8 ++++----
.../deployment/resource-providers/standalone/kubernetes.md | 2 +-
.../deployment/resource-providers/standalone/overview.md | 8 ++++----
docs/content.zh/docs/deployment/resource-providers/yarn.md | 2 +-
docs/content.zh/docs/deployment/security/security-ssl.md | 2 +-
docs/content.zh/docs/deployment/trace_reporters.md | 2 +-
docs/content.zh/docs/dev/datastream/execution/parallel.md | 2 +-
.../docs/dev/datastream/fault-tolerance/checkpointing.md | 2 +-
.../docs/dev/datastream/fault-tolerance/state_backends.md | 2 +-
docs/content.zh/docs/dev/table/catalogs.md | 4 ++--
.../docs/dev/table/hive-compatibility/hiveserver2.md | 4 ++--
docs/content.zh/docs/dev/table/sql-gateway/overview.md | 4 ++--
docs/content.zh/docs/dev/table/sqlClient.md | 2 +-
docs/content.zh/docs/ops/debugging/flame_graphs.md | 2 +-
docs/content.zh/docs/ops/metrics.md | 4 ++--
docs/content.zh/docs/ops/rest_api.md | 2 +-
docs/content.zh/docs/ops/state/state_backends.md | 14 +++++++-------
docs/content.zh/docs/ops/state/task_failure_recovery.md | 8 ++++----
.../docs/try-flink/flink-operations-playground.md | 4 ++--
.../deployment/resource-providers/standalone/docker.md | 2 +-
docs/content/docs/deployment/resource-providers/yarn.md | 2 +-
.../docs/dev/datastream/fault-tolerance/state_backends.md | 2 +-
docs/content/docs/dev/table/sqlClient.md | 2 +-
docs/content/docs/ops/state/task_failure_recovery.md | 4 ++--
36 files changed, 73 insertions(+), 73 deletions(-)
diff --git a/docs/content.zh/docs/connectors/table/filesystem.md
b/docs/content.zh/docs/connectors/table/filesystem.md
index 17d05045a20..584f5009081 100644
--- a/docs/content.zh/docs/connectors/table/filesystem.md
+++ b/docs/content.zh/docs/connectors/table/filesystem.md
@@ -241,8 +241,8 @@ CREATE TABLE MyUserTableWithFilepath (
**注意：** 对于 bulk formats 数据 (parquet、orc、avro)，滚动策略与 checkpoint 间隔（pending
状态的文件会在下个 checkpoint 完成）控制了 part 文件的大小和个数。
-**注意：** 对于 row formats 数据 (csv、json)，如果想使得分区文件更快在文件系统中可见，可以设置
`sink.rolling-policy.file-size` 或 `sink.rolling-policy.rollover-interval` 属性以及在
[Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file" >}}) 中的
`execution.checkpointing.interval` 属性。
-对于其他 formats (avro、orc)，可以只设置 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中的
`execution.checkpointing.interval` 属性。
+**注意：** 对于 row formats 数据 (csv、json)，如果想使得分区文件更快在文件系统中可见，可以设置
`sink.rolling-policy.file-size` 或 `sink.rolling-policy.rollover-interval` 属性以及在
[Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}}) 中的
`execution.checkpointing.interval` 属性。
+对于其他 formats (avro、orc)，可以只设置 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 中的 `execution.checkpointing.interval`
属性。
<a name="file-compaction"></a>
diff --git a/docs/content.zh/docs/deployment/advanced/historyserver.md
b/docs/content.zh/docs/deployment/advanced/historyserver.md
index 16950b4a06b..bef18431585 100644
--- a/docs/content.zh/docs/deployment/advanced/historyserver.md
+++ b/docs/content.zh/docs/deployment/advanced/historyserver.md
@@ -58,7 +58,7 @@ bin/historyserver.sh (start|start-foreground|stop)
**JobManager**
-已完成作业的存档在 JobManager 上进行，将已存档的作业信息上传到文件系统目录中。你可以在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}})中通过
`jobmanager.archive.fs.dir` 设置一个目录存档已完成的作业。
+已完成作业的存档在 JobManager 上进行，将已存档的作业信息上传到文件系统目录中。你可以在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}})中通过 `jobmanager.archive.fs.dir`
设置一个目录存档已完成的作业。
```yaml
# 上传已完成作业信息的目录
diff --git a/docs/content.zh/docs/deployment/cli.md
b/docs/content.zh/docs/deployment/cli.md
index 64196be5da1..b8f7c2f5aaf 100644
--- a/docs/content.zh/docs/deployment/cli.md
+++ b/docs/content.zh/docs/deployment/cli.md
@@ -30,7 +30,7 @@ under the License.
Flink provides a Command-Line Interface (CLI) `bin/flink` to run programs that
are packaged as JAR files and to control their execution. The CLI is part of
any
Flink setup, available in local single node setups and in distributed setups.
-It connects to the running JobManager specified in [Flink configuration
file]({{< ref "docs/deployment/config#flink-configuration-file" >}}).
+It connects to the running JobManager specified in [Flink configuration
file]({{< ref "docs/deployment/config#flink-配置文件" >}}).
@@ -431,7 +431,7 @@ parameter combinations:
* `./bin/flink run --target remote`: Submission to an already running Flink
cluster
The `--target` will overwrite the [execution.target]({{< ref
"docs/deployment/config" >}}#execution-target)
-specified in the [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}).
+specified in the [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}).
For more details on the commands and the available options, please refer to
the Resource Provider-specific
pages of the documentation.
diff --git a/docs/content.zh/docs/deployment/filesystems/azure.md
b/docs/content.zh/docs/deployment/filesystems/azure.md
index 76b34fb6a3d..f3ef479254d 100644
--- a/docs/content.zh/docs/deployment/filesystems/azure.md
+++ b/docs/content.zh/docs/deployment/filesystems/azure.md
@@ -86,13 +86,13 @@ cp ./opt/flink-azure-fs-hadoop-{{< version >}}.jar
./plugins/azure-fs-hadoop/
### WASB
Hadoop 的 WASB Azure 文件系统支持通过 Hadoop 配置来配置凭据，如 [Hadoop Azure Blob Storage
文档](https://hadoop.apache.org/docs/current/hadoop-azure/index.html#Configuring_Credentials)
所述。
-为方便起见，Flink 将所有的 Flink 配置添加 `fs.azure` 键前缀后转发至文件系统的 Hadoop 配置中。因此，可通过以下方法在
[Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file" >}}) 中配置
Azure Blob 存储密钥：
+为方便起见，Flink 将所有的 Flink 配置添加 `fs.azure` 键前缀后转发至文件系统的 Hadoop 配置中。因此，可通过以下方法在
[Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}}) 中配置 Azure Blob
存储密钥：
```yaml
fs.azure.account.key.<account_name>.blob.core.windows.net: <azure_storage_key>
```
-或者通过在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file"
>}}) 中设置以下配置键，将文件系统配置为从环境变量 `AZURE_STORAGE_KEY` 读取 Azure Blob 存储密钥：
+或者通过在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})
中设置以下配置键，将文件系统配置为从环境变量 `AZURE_STORAGE_KEY` 读取 Azure Blob 存储密钥：
```yaml
fs.azure.account.keyprovider.<account_name>.blob.core.windows.net:
org.apache.flink.fs.azurefs.EnvironmentVariableKeyProvider
@@ -107,7 +107,7 @@ Azure 推荐使用 Azure 托管身份来使用 abfs 访问 ADLS Gen2 存储帐
{{< /hint >}}
##### 使用存储密钥访问ABFS(不鼓励)
-Azure blob 存储密钥可以通过以下方式在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中配置：
+Azure blob 存储密钥可以通过以下方式在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 中配置：
```yaml
fs.azure.account.key.<account_name>.dfs.core.windows.net: <azure_storage_key>
diff --git a/docs/content.zh/docs/deployment/filesystems/gcs.md
b/docs/content.zh/docs/deployment/filesystems/gcs.md
index ab8cc6a83de..ed889c5ec60 100644
--- a/docs/content.zh/docs/deployment/filesystems/gcs.md
+++ b/docs/content.zh/docs/deployment/filesystems/gcs.md
@@ -71,13 +71,13 @@ cp ./opt/flink-gs-fs-hadoop-{{< version >}}.jar
./plugins/gs-fs-hadoop/
### Configuration
-The underlying Hadoop file system can be configured using the [Hadoop
configuration
keys](https://github.com/GoogleCloudDataproc/hadoop-connectors/blob/v2.2.18/gcs/CONFIGURATION.md)
for `gcs-connector` by adding the configurations to your [Flink configuration
file]({{< ref "docs/deployment/config#flink-configuration-file" >}}).
+The underlying Hadoop file system can be configured using the [Hadoop
configuration
keys](https://github.com/GoogleCloudDataproc/hadoop-connectors/blob/v2.2.18/gcs/CONFIGURATION.md)
for `gcs-connector` by adding the configurations to your [Flink configuration
file]({{< ref "docs/deployment/config#flink-配置文件" >}}).
-For example, `gcs-connector` has a `fs.gs.http.connect-timeout` configuration
key. If you want to change it, you need to set `gs.http.connect-timeout: xyz`
in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}). Flink will internally
translate this back to `fs.gs.http.connect-timeout`.
+For example, `gcs-connector` has a `fs.gs.http.connect-timeout` configuration
key. If you want to change it, you need to set `gs.http.connect-timeout: xyz`
in [Flink configuration file]({{< ref "docs/deployment/config#flink-配置文件" >}}).
Flink will internally translate this back to `fs.gs.http.connect-timeout`.
You can also set `gcs-connector` options directly in the Hadoop
`core-site.xml` configuration file, so long as the Hadoop configuration
directory is made known to Flink via the `env.hadoop.conf.dir` Flink option or
via the `HADOOP_CONF_DIR` environment variable.
-`flink-gs-fs-hadoop` can also be configured by setting the following options
in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}):
+`flink-gs-fs-hadoop` can also be configured by setting the following options
in [Flink configuration file]({{< ref "docs/deployment/config#flink-配置文件" >}}):
| Key | Description
[...]
|---------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
diff --git a/docs/content.zh/docs/deployment/filesystems/oss.md
b/docs/content.zh/docs/deployment/filesystems/oss.md
index 849859fb148..414372e06ea 100644
--- a/docs/content.zh/docs/deployment/filesystems/oss.md
+++ b/docs/content.zh/docs/deployment/filesystems/oss.md
@@ -70,11 +70,11 @@ cp ./opt/flink-oss-fs-hadoop-{{< version >}}.jar
./plugins/oss-fs-hadoop/
在设置好 OSS 文件系统包装器之后，需要添加一些配置以保证 Flink 有权限访问 OSS buckets。
-为了简单使用，可直接在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中使用与 Hadoop
`core-site.xml` 相同的配置关键字。
+为了简单使用，可直接在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}}) 中使用与
Hadoop `core-site.xml` 相同的配置关键字。
可在 [Hadoop OSS
文档](http://hadoop.apache.org/docs/current/hadoop-aliyun/tools/hadoop-aliyun/index.html)
中查看配置关键字。
-一些配置必须添加至 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) （**在 Hadoop OSS
文档中定义的其它配置为用作性能调优的高级配置**）：
+一些配置必须添加至 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}}) （**在
Hadoop OSS 文档中定义的其它配置为用作性能调优的高级配置**）：
```yaml
fs.oss.endpoint: 连接的 Aliyun OSS endpoint
@@ -82,7 +82,7 @@ fs.oss.accessKeyId: Aliyun access key ID
fs.oss.accessKeySecret: Aliyun access key secret
```
-备选的 `CredentialsProvider` 也可在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中配置，例如：
+备选的 `CredentialsProvider` 也可在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 中配置，例如：
```yaml
# 从 OSS_ACCESS_KEY_ID 和 OSS_ACCESS_KEY_SECRET 读取凭据 (Credentials)
fs.oss.credentials.provider:
com.aliyun.oss.common.auth.EnvironmentVariableCredentialsProvider
diff --git a/docs/content.zh/docs/deployment/filesystems/s3.md
b/docs/content.zh/docs/deployment/filesystems/s3.md
index 7605fb54338..f409de2724a 100644
--- a/docs/content.zh/docs/deployment/filesystems/s3.md
+++ b/docs/content.zh/docs/deployment/filesystems/s3.md
@@ -66,12 +66,12 @@ env.configure(config);
Flink 提供两种文件系统用来与 S3 交互：`flink-s3-fs-presto` 和
`flink-s3-fs-hadoop`。两种实现都是独立的且没有依赖项，因此使用时无需将 Hadoop 添加至 classpath。
- `flink-s3-fs-presto`，通过 *s3://* 和 *s3p://* 两种 scheme 使用，基于 [Presto
project](https://prestodb.io/)。
- 可以使用[和 Presto
文件系统相同的配置项](https://prestodb.io/docs/0.272/connector/hive.html#amazon-s3-configuration)进行配置，方式为将配置添加到
[Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file"
>}})中。如果要在 S3 中使用 checkpoint，推荐使用 Presto S3 文件系统。
+ 可以使用[和 Presto
文件系统相同的配置项](https://prestodb.io/docs/0.272/connector/hive.html#amazon-s3-configuration)进行配置，方式为将配置添加到
[Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})中。如果要在 S3 中使用
checkpoint，推荐使用 Presto S3 文件系统。
- `flink-s3-fs-hadoop`，通过 *s3://* 和 *s3a://* 两种 scheme 使用, 基于 [Hadoop
Project](https://hadoop.apache.org/)。
- 本文件系统可以使用类似 [Hadoop S3A
的配置项](https://hadoop.apache.org/docs/stable/hadoop-aws/tools/hadoop-aws/index.html#S3A)进行配置，方式为将配置添加到
[Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file" >}})中。
+ 本文件系统可以使用类似 [Hadoop S3A
的配置项](https://hadoop.apache.org/docs/stable/hadoop-aws/tools/hadoop-aws/index.html#S3A)进行配置，方式为将配置添加到
[Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})中。
- 例如，Hadoop 有 `fs.s3a.connection.maximum` 的配置选项。 如果你想在 Flink
程序中改变该配置的值，你需要将配置 `s3.connection.maximum: xyz` 添加到 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}})中。Flink 会内部将其转换成配置
`fs.s3a.connection.maximum`。 而无需通过 Hadoop 的 XML 配置文件来传递参数。
+ 例如，Hadoop 有 `fs.s3a.connection.maximum` 的配置选项。 如果你想在 Flink
程序中改变该配置的值，你需要将配置 `s3.connection.maximum: xyz` 添加到 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}})中。Flink 会内部将其转换成配置
`fs.s3a.connection.maximum`。 而无需通过 Hadoop 的 XML 配置文件来传递参数。
另外，它是唯一支持 [FileSystem]({{< ref "docs/connectors/datastream/filesystem"
>}}) 的 S3 文件系统。
@@ -99,7 +99,7 @@ cp ./opt/flink-s3-fs-presto-{{< version >}}.jar
./plugins/s3-fs-presto/
可以通过**访问密钥对（access and secret key）**授予 S3 访问权限。请注意，根据 [Introduction of IAM
roles](https://blogs.aws.amazon.com/security/post/Tx1XG3FX6VMU6O5/A-safer-way-to-distribute-AWS-credentials-to-EC2)，不推荐使用该方法。
- `s3.access-key` 和 `s3.secret-key` 均需要在 Flink 的 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中进行配置：
+ `s3.access-key` 和 `s3.secret-key` 均需要在 Flink 的 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 中进行配置：
```yaml
s3.access-key: your-access-key
@@ -108,7 +108,7 @@ s3.secret-key: your-secret-key
## 配置非 S3 访问点
-S3 文件系统还支持兼容 S3 的对象存储服务，如 [IBM's Cloud Object
Storage](https://www.ibm.com/cloud/object-storage) 和
[Minio](https://min.io/)。可在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中配置使用的访问点：
+S3 文件系统还支持兼容 S3 的对象存储服务，如 [IBM's Cloud Object
Storage](https://www.ibm.com/cloud/object-storage) 和
[Minio](https://min.io/)。可在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 中配置使用的访问点：
```yaml
s3.endpoint: your-endpoint-hostname
@@ -116,7 +116,7 @@ s3.endpoint: your-endpoint-hostname
## 配置路径样式的访问
-某些兼容 S3 的对象存储服务可能没有默认启用虚拟主机样式的寻址。这种情况下需要在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中添加配置以启用路径样式的访问：
+某些兼容 S3 的对象存储服务可能没有默认启用虚拟主机样式的寻址。这种情况下需要在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 中添加配置以启用路径样式的访问：
```yaml
s3.path.style.access: true
diff --git a/docs/content.zh/docs/deployment/ha/kubernetes_ha.md
b/docs/content.zh/docs/deployment/ha/kubernetes_ha.md
index 40da006218c..b6e9bf36277 100644
--- a/docs/content.zh/docs/deployment/ha/kubernetes_ha.md
+++ b/docs/content.zh/docs/deployment/ha/kubernetes_ha.md
@@ -67,7 +67,7 @@ kubernetes.cluster-id: cluster1337
### 配置示例
-在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file" >}})
中配置高可用模式:
+在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}}) 中配置高可用模式:
```yaml
kubernetes.cluster-id: <cluster-id>
diff --git a/docs/content.zh/docs/deployment/ha/zookeeper_ha.md
b/docs/content.zh/docs/deployment/ha/zookeeper_ha.md
index 705da25acbd..edd7ab6a4a0 100644
--- a/docs/content.zh/docs/deployment/ha/zookeeper_ha.md
+++ b/docs/content.zh/docs/deployment/ha/zookeeper_ha.md
@@ -68,7 +68,7 @@ Flink 利用 **[ZooKeeper](http://zookeeper.apache.org)** 在所有运行的
Job
### 配置示例
-在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file" >}})
中配置高可用模式和 ZooKeeper 复制组（quorum）:
+在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}}) 中配置高可用模式和
ZooKeeper 复制组（quorum）:
```bash
high-availability.type: zookeeper
@@ -82,7 +82,7 @@ high-availability.storageDir: hdfs:///flink/recovery
## ZooKeeper 安全配置
-如果 ZooKeeper 使用 Kerberos 以安全模式运行，必要时可以在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中覆盖以下配置:
+如果 ZooKeeper 使用 Kerberos 以安全模式运行，必要时可以在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 中覆盖以下配置:
```bash
# 默认配置为 "zookeeper". 如果 ZooKeeper quorum 配置了不同的服务名称，
diff --git a/docs/content.zh/docs/deployment/memory/mem_migration.md
b/docs/content.zh/docs/deployment/memory/mem_migration.md
index c1a7059475f..7b43848e8a9 100644
--- a/docs/content.zh/docs/deployment/memory/mem_migration.md
+++ b/docs/content.zh/docs/deployment/memory/mem_migration.md
@@ -290,7 +290,7 @@ Flink 通过设置上述 JVM 内存限制降低内存泄漏问题的排查难度
## Flink 配置文件中的默认配置
-本节描述 Flink 自带的默认 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}})中的变化。
+本节描述 Flink 自带的默认 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件"
>}})中的变化。
原本的 TaskManager 总内存（`taskmanager.heap.size`）被新的配置项
[`taskmanager.memory.process.size`]({{< ref "docs/deployment/config"
>}}#taskmanager-memory-process-size) 所取代。
默认值从 1024MB 增加到了 1728MB。
@@ -301,5 +301,5 @@ Flink 通过设置上述 JVM 内存限制降低内存泄漏问题的排查难度
请参考[如何配置总内存]({{< ref "docs/deployment/memory/mem_setup"
>}}#configure-total-memory)。
{{< hint warning >}}
-**注意：** 使用新的默认 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}})
可能会造成各内存部分的大小发生变化，从而产生性能变化。
+**注意：** 使用新的默认 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})
可能会造成各内存部分的大小发生变化，从而产生性能变化。
{{< /hint >}}
diff --git a/docs/content.zh/docs/deployment/metric_reporters.md
b/docs/content.zh/docs/deployment/metric_reporters.md
index 7413f7cc581..23f1d4b674e 100644
--- a/docs/content.zh/docs/deployment/metric_reporters.md
+++ b/docs/content.zh/docs/deployment/metric_reporters.md
@@ -31,7 +31,7 @@ under the License.
Flink 支持用户将 Flink 的各项运行时指标发送给外部系统。
了解更多指标方面信息可查看 [metric 系统相关文档]({{< ref "docs/ops/metrics" >}})。
-你可以通过 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file"
>}})来配置一种或多种发送器，将运行时指标暴露给外部系统。
+你可以通过 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件"
>}})来配置一种或多种发送器，将运行时指标暴露给外部系统。
发送器会在 TaskManager、Flink 作业启动时进行实例化。
下面列出了所有发送器都适用的参数，可以通过配置文件中的 `metrics.reporter.<reporter_name>.<property>`
项进行配置。有些发送器有自己特有的配置，详见该发送器章节下的具体说明。
diff --git
a/docs/content.zh/docs/deployment/resource-providers/native_kubernetes.md
b/docs/content.zh/docs/deployment/resource-providers/native_kubernetes.md
index 5876cbeab7c..d8ca037d441 100644
--- a/docs/content.zh/docs/deployment/resource-providers/native_kubernetes.md
+++ b/docs/content.zh/docs/deployment/resource-providers/native_kubernetes.md
@@ -140,7 +140,7 @@ $ ./bin/flink list --target kubernetes-application
-Dkubernetes.cluster-id=my-fi
$ ./bin/flink cancel --target kubernetes-application
-Dkubernetes.cluster-id=my-first-application-cluster <jobId>
```
-You can override configurations set in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) by passing key-value
pairs `-Dkey=value` to `bin/flink`.
+You can override configurations set in [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}) by passing key-value pairs
`-Dkey=value` to `bin/flink`.
### Per-Job Cluster Mode
@@ -166,7 +166,7 @@ $ ./bin/kubernetes-session.sh \
-Dexecution.attached=true
```
-You can override configurations set in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) by passing key-value
pairs `-Dkey=value` to `bin/kubernetes-session.sh`.
+You can override configurations set in [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}) by passing key-value pairs
`-Dkey=value` to `bin/kubernetes-session.sh`.
#### Stop a Running Session Cluster
diff --git
a/docs/content.zh/docs/deployment/resource-providers/standalone/docker.md
b/docs/content.zh/docs/deployment/resource-providers/standalone/docker.md
index 06adb8c0a42..b618b411303 100644
--- a/docs/content.zh/docs/deployment/resource-providers/standalone/docker.md
+++ b/docs/content.zh/docs/deployment/resource-providers/standalone/docker.md
@@ -491,7 +491,7 @@ $ docker run flink:{{< stable >}}{{< version >}}-scala{{<
scala_version >}}{{< /
-D blob.server.port=6124
```
-Options set via dynamic properties overwrite the options from [Flink
configuration file]({{< ref "docs/deployment/config#flink-configuration-file"
>}}).
+Options set via dynamic properties overwrite the options from [Flink
configuration file]({{< ref "docs/deployment/config#flink-配置文件" >}}).
### Via Environment Variables
@@ -508,11 +508,11 @@ $ docker run --env FLINK_PROPERTIES=${FLINK_PROPERTIES}
flink:{{< stable >}}{{<
The [`jobmanager.rpc.address`]({{< ref "docs/deployment/config"
>}}#jobmanager-rpc-address) option must be configured, others are optional to
set.
The environment variable `FLINK_PROPERTIES` should contain a list of Flink
cluster configuration options separated by new line,
-the same way as in the [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}). `FLINK_PROPERTIES`
takes precedence over configurations in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}).
+the same way as in the [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}). `FLINK_PROPERTIES` takes precedence
over configurations in [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}).
### Via Flink configuration file
-The configuration files ([Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}), logging, hosts etc) are
located in the `/opt/flink/conf` directory in the Flink image.
+The configuration files ([Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}), logging, hosts etc) are located in
the `/opt/flink/conf` directory in the Flink image.
To provide a custom location for the Flink configuration files, you can
* **either mount a volume** with the custom configuration files to this path
`/opt/flink/conf` when you run the Flink image:
@@ -534,7 +534,7 @@ To provide a custom location for the Flink configuration
files, you can
{{< hint info >}}
The mounted volume must contain all necessary configuration files.
-The [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) file must have write
permission so that the Docker entry point script can modify it in certain cases.
+The [Flink configuration file]({{< ref "docs/deployment/config#flink-配置文件"
>}}) must have write permission so that the Docker entry point script can
modify it in certain cases.
{{< /hint >}}
### Using Filesystem Plugins
diff --git
a/docs/content.zh/docs/deployment/resource-providers/standalone/kubernetes.md
b/docs/content.zh/docs/deployment/resource-providers/standalone/kubernetes.md
index a3f5edce0b9..701dd11d111 100644
---
a/docs/content.zh/docs/deployment/resource-providers/standalone/kubernetes.md
+++
b/docs/content.zh/docs/deployment/resource-providers/standalone/kubernetes.md
@@ -158,7 +158,7 @@ $ ./bin/flink run -m localhost:8081
./examples/streaming/TopSpeedWindowing.jar
### Configuration
-所有配置项都展示在[配置页面]({{< ref "docs/deployment/config" >}})上。在 config map 配置文件
`flink-configuration-configmap.yaml` 中，可以将配置添加在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 部分。
+所有配置项都展示在[配置页面]({{< ref "docs/deployment/config" >}})上。在 config map 配置文件
`flink-configuration-configmap.yaml` 中，可以将配置添加在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 部分。
<a name="accessing-flink-in-kubernetes"></a>
diff --git
a/docs/content.zh/docs/deployment/resource-providers/standalone/overview.md
b/docs/content.zh/docs/deployment/resource-providers/standalone/overview.md
index fd658ba5c4d..3ed9e070950 100644
--- a/docs/content.zh/docs/deployment/resource-providers/standalone/overview.md
+++ b/docs/content.zh/docs/deployment/resource-providers/standalone/overview.md
@@ -61,7 +61,7 @@ Flink 运行在所有*类 UNIX 环境*下，例如 **Linux**，**Mac OS X** 和
Flink 需要 master 和所有 worker 节点设置 `JAVA_HOME` 环境变量，并指向你的 Java 安装目录。
-你可以在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file"
>}})中通过 `env.java.home` 配置项来设置此变量。 需要注意的是，该配置项必须以 flattened 的格式（即一行键值对格式）在配置文件中。
+你可以在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})中通过
`env.java.home` 配置项来设置此变量。 需要注意的是，该配置项必须以 flattened 的格式（即一行键值对格式）在配置文件中。
{{< top >}}
@@ -82,11 +82,11 @@ cd flink-*
### 配置 Flink
-在解压完文件后，你需要编辑 [*Flink 配置文件*]({{< ref
"docs/deployment/config#flink-configuration-file" >}})来为集群配置 Flink。
+在解压完文件后，你需要编辑 [*Flink 配置文件*]({{< ref "docs/deployment/config#flink-配置文件"
>}})来为集群配置 Flink。
设置 `jobmanager.rpc.address` 配置项指向 master 节点。你也应该通过设置
`jobmanager.memory.process.size` 和 `taskmanager.memory.process.size` 配置项来定义
Flink 允许在每个节点上分配的最大内存值。
-这些值的单位是 MB。如果一些 worker 节点上有你想分配到 Flink 系统的多余内存，你可以在这些特定节点的 [*Flink 配置文件*]({{<
ref "docs/deployment/config#flink-configuration-file" >}}) 文件中重写
`taskmanager.memory.process.size` 或 `taskmanager.memory.flink.size` 的默认值。
+这些值的单位是 MB。如果一些 worker 节点上有你想分配到 Flink 系统的多余内存，你可以在这些特定节点的 [*Flink 配置文件*]({{<
ref "docs/deployment/config#flink-配置文件" >}}) 中重写
`taskmanager.memory.process.size` 或 `taskmanager.memory.flink.size` 的默认值。
最后，你必须提供集群上会被用作为 worker 节点的所有节点列表，也就是运行 TaskManager 的节点。编辑文件 *conf/workers*
并输入每个 worker 节点的 IP 或主机名。
@@ -192,7 +192,7 @@ By default, the job manager will pick a *random port* for
inter process communic
### Example: Standalone Cluster with 2 JobManagers
-1. **Configure high availability mode and ZooKeeper quorum** in [Flink
configuration file]({{< ref "docs/deployment/config#flink-configuration-file"
>}}):
+1. **Configure high availability mode and ZooKeeper quorum** in [Flink
configuration file]({{< ref "docs/deployment/config#flink-配置文件" >}}):
<pre>
high-availability.type: zookeeper
diff --git a/docs/content.zh/docs/deployment/resource-providers/yarn.md
b/docs/content.zh/docs/deployment/resource-providers/yarn.md
index 94970b8fa5b..cf68314288f 100644
--- a/docs/content.zh/docs/deployment/resource-providers/yarn.md
+++ b/docs/content.zh/docs/deployment/resource-providers/yarn.md
@@ -166,7 +166,7 @@ You can **re-attach to a YARN session** using the following
command:
./bin/yarn-session.sh -id application_XXXX_YY
```
-Besides passing [configuration]({{< ref "docs/deployment/config" >}}) via the
[Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) file, you can also pass
any configuration at submission time to the `./bin/yarn-session.sh` client
using `-Dkey=value` arguments.
+Besides passing [configuration]({{< ref "docs/deployment/config" >}}) via the
[Flink configuration file]({{< ref "docs/deployment/config#flink-配置文件" >}}) ,
you can also pass any configuration at submission time to the
`./bin/yarn-session.sh` client using `-Dkey=value` arguments.
The YARN session client also has a few "shortcut arguments" for commonly used
settings. They can be listed with `./bin/yarn-session.sh -h`.
diff --git a/docs/content.zh/docs/deployment/security/security-ssl.md
b/docs/content.zh/docs/deployment/security/security-ssl.md
index e585ad66664..4b18ad983dc 100644
--- a/docs/content.zh/docs/deployment/security/security-ssl.md
+++ b/docs/content.zh/docs/deployment/security/security-ssl.md
@@ -266,7 +266,7 @@ $ keytool -importcert -keystore rest.signed.keystore
-storepass rest_keystore_pa
$ keytool -importcert -keystore rest.signed.keystore -storepass
rest_keystore_password -file rest.cer -alias flink.rest -noprompt
```
-Now add the following configuration to your [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}):
+Now add the following configuration to your [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}):
```yaml
security.ssl.rest.enabled: true
diff --git a/docs/content.zh/docs/deployment/trace_reporters.md
b/docs/content.zh/docs/deployment/trace_reporters.md
index bfbb038c240..f64210eeb33 100644
--- a/docs/content.zh/docs/deployment/trace_reporters.md
+++ b/docs/content.zh/docs/deployment/trace_reporters.md
@@ -29,7 +29,7 @@ under the License.
Flink allows reporting traces to external systems.
For more information about Flink's tracing system go to the [tracing system
documentation]({{< ref "docs/ops/traces" >}}).
-Traces can be exposed to an external system by configuring one or several
reporters in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}). These
+Traces can be exposed to an external system by configuring one or several
reporters in [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}). These
reporters will be instantiated on each job and task manager when they are
started.
Below is a list of parameters that are generally applicable to all reporters.
diff --git a/docs/content.zh/docs/dev/datastream/execution/parallel.md
b/docs/content.zh/docs/dev/datastream/execution/parallel.md
index 6b2f120d875..e75fa76d6f7 100644
--- a/docs/content.zh/docs/dev/datastream/execution/parallel.md
+++ b/docs/content.zh/docs/dev/datastream/execution/parallel.md
@@ -206,7 +206,7 @@ Python API 中尚不支持该特性。
### 系统层次
-可以通过设置 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file"
>}})中的 `parallelism.default` 参数，在系统层次来指定所有执行环境的默认并行度。你可以通过查阅[配置文档]({{< ref
"docs/deployment/config" >}})获取更多细节。
+可以通过设置 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})中的
`parallelism.default` 参数，在系统层次来指定所有执行环境的默认并行度。你可以通过查阅[配置文档]({{< ref
"docs/deployment/config" >}})获取更多细节。
## 设置最大并行度
diff --git
a/docs/content.zh/docs/dev/datastream/fault-tolerance/checkpointing.md
b/docs/content.zh/docs/dev/datastream/fault-tolerance/checkpointing.md
index 4a94f9c3ab1..b8148aaae10 100644
--- a/docs/content.zh/docs/dev/datastream/fault-tolerance/checkpointing.md
+++ b/docs/content.zh/docs/dev/datastream/fault-tolerance/checkpointing.md
@@ -182,7 +182,7 @@ env.get_checkpoint_config().enable_unaligned_checkpoints()
### 相关的配置选项
-更多的属性与默认值能在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中设置（完整教程请阅读 [配置]({{< ref
"docs/deployment/config" >}})）。
+更多的属性与默认值能在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})
中设置（完整教程请阅读 [配置]({{< ref "docs/deployment/config" >}})）。
{{< generated/checkpointing_configuration >}}
diff --git
a/docs/content.zh/docs/dev/datastream/fault-tolerance/state_backends.md
b/docs/content.zh/docs/dev/datastream/fault-tolerance/state_backends.md
index 6a71b906f3b..2fcbae4ec1a 100644
--- a/docs/content.zh/docs/dev/datastream/fault-tolerance/state_backends.md
+++ b/docs/content.zh/docs/dev/datastream/fault-tolerance/state_backends.md
@@ -30,7 +30,7 @@ Flink 提供了多种 state backends，它用于指定状态的存储方式和
状态可以位于 Java 的堆或堆外内存。取决于你的 state backend，Flink 也可以自己管理应用程序的状态。
为了让应用程序可以维护非常大的状态，Flink 可以自己管理内存（如果有必要可以溢写到磁盘）。
-默认情况下，所有 Flink Job 会使用配置文件 [*Flink 配置文件*]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中指定的 state backend。
+默认情况下，所有 Flink Job 会使用 [*Flink 配置文件*]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 中指定的 state backend。
但是，配置文件中指定的默认 state backend 会被 Job 中指定的 state backend 覆盖，如下所示。
diff --git a/docs/content.zh/docs/dev/table/catalogs.md
b/docs/content.zh/docs/dev/table/catalogs.md
index 34ed574d158..bcfd41231ce 100644
--- a/docs/content.zh/docs/dev/table/catalogs.md
+++ b/docs/content.zh/docs/dev/table/catalogs.md
@@ -839,7 +839,7 @@ TableEnvironment env = TableEnvironment.create(
env.executeSql("CREATE TABLE ...").wait();
```
-For sql-gateway, you can add the option `table.catalog-modification.listeners`
in the [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) and start
+For sql-gateway, you can add the option `table.catalog-modification.listeners`
in the [Flink configuration file]({{< ref "docs/deployment/config#flink-配置文件"
>}}) and start
the gateway, or you can also start sql-gateway with dynamic parameter, then
you can use sql-client to perform ddl directly.
## Catalog Store
@@ -879,7 +879,7 @@ final EnvironmentSettings settings =
final TableEnvironment tableEnv = TableEnvironment.create(settings);
```
-在 SQL Gateway 中，推荐在 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}})中进行配置，所有的 session
可以自动使用已经创建好的 Catalog 。
+在 SQL Gateway 中，推荐在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件"
>}})中进行配置，所有的 session 可以自动使用已经创建好的 Catalog 。
配置的格式如下，一般情况下需要配置 Catalog Store 的 kind ，以及 Catalog Store 需要的其他参数配置。
```yaml
table.catalog-store.kind: file
diff --git a/docs/content.zh/docs/dev/table/hive-compatibility/hiveserver2.md
b/docs/content.zh/docs/dev/table/hive-compatibility/hiveserver2.md
index c60748d807a..030506633cd 100644
--- a/docs/content.zh/docs/dev/table/hive-compatibility/hiveserver2.md
+++ b/docs/content.zh/docs/dev/table/hive-compatibility/hiveserver2.md
@@ -38,7 +38,7 @@ The HiveServer2 Endpoint is not the default endpoint for the
SQL Gateway. You ca
$ ./bin/sql-gateway.sh start -Dsql-gateway.endpoint.type=hiveserver2
-Dsql-gateway.endpoint.hiveserver2.catalog.hive-conf-dir=<path to hive conf>
```
-or add the following configuration into [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) (please replace the
`<path to hive conf>` with your hive conf path).
+or add the following configuration into [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}) (please replace the `<path to hive
conf>` with your hive conf path).
```yaml
sql-gateway.endpoint.type: hiveserver2
@@ -313,4 +313,4 @@ Supported Types
The HiveServer2 Endpoint is built on the Hive2 now and supports all Hive2
available types. For Hive-compatible tables, the HiveServer2 Endpoint
obeys the same rule as the HiveCatalog to convert the Flink types to Hive
Types and serialize them to the thrift object. Please refer to
-the [HiveCatalog]({{< ref
"docs/connectors/table/hive/hive_catalog#supported-types" >}}) for the type
mappings.
\ No newline at end of file
+the [HiveCatalog]({{< ref
"docs/connectors/table/hive/hive_catalog#supported-types" >}}) for the type
mappings.
diff --git a/docs/content.zh/docs/dev/table/sql-gateway/overview.md
b/docs/content.zh/docs/dev/table/sql-gateway/overview.md
index 5c979168655..7848ed64a2d 100644
--- a/docs/content.zh/docs/dev/table/sql-gateway/overview.md
+++ b/docs/content.zh/docs/dev/table/sql-gateway/overview.md
@@ -237,14 +237,14 @@ SQL Gateway 默认集成 REST Endpoint。由于架构的可扩展性，用户可
$ ./bin/sql-gateway.sh start -Dsql-gateway.endpoint.type=hiveserver2
```
-或者在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file"
>}}) 中增加如下配置：
+或者在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}}) 中增加如下配置：
```yaml
sql-gateway.endpoint.type: hiveserver2
```
{{< hint info >}}
-Notice: 如果 CLI 命令和 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 都有
`sql-gateway.endpoint.type`，CLI 的优先级比 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 更高。
+Notice: 如果 CLI 命令和 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件"
>}}) 都有 `sql-gateway.endpoint.type`，CLI 的优先级比 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 更高。
{{< /hint >}}
具体的 endpoint 请参考相应页面。
diff --git a/docs/content.zh/docs/dev/table/sqlClient.md
b/docs/content.zh/docs/dev/table/sqlClient.md
index f12bb7e6375..6df3bedefbd 100644
--- a/docs/content.zh/docs/dev/table/sqlClient.md
+++ b/docs/content.zh/docs/dev/table/sqlClient.md
@@ -82,7 +82,7 @@ Cache-Control: no-cache
EOF)
```
-By default, the SQL Client will use the truststore configured using the
`security.ssl.rest.truststore` and `security.ssl.rest.truststore-password`
properties in the [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) file on the SQL client
side. If these properties aren't explicitly configured, the client will use the
default certificate stores provided by the JDK.
+By default, the SQL Client will use the truststore configured using the
`security.ssl.rest.truststore` and `security.ssl.rest.truststore-password`
properties in the [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}) on the SQL client side. If these
properties aren't explicitly configured, the client will use the default
certificate stores provided by the JDK.
<span class="label label-danger">Note</span> SQL 客户端目前只支持和 REST API 版本大于 v1 的
[REST Endpoint]({{< ref "docs/dev/table/sql-gateway/rest" >}}#rest-api) 通信。
diff --git a/docs/content.zh/docs/ops/debugging/flame_graphs.md
b/docs/content.zh/docs/ops/debugging/flame_graphs.md
index ca41d0c7c4f..6a030dff12e 100644
--- a/docs/content.zh/docs/ops/debugging/flame_graphs.md
+++ b/docs/content.zh/docs/ops/debugging/flame_graphs.md
@@ -48,7 +48,7 @@ Operator's On-CPU Flame Graph
{{< hint warning >}}
-Any measurement process in and of itself inevitably affects the subject of
measurement (see the [double-split
experiment](https://en.wikipedia.org/wiki/Double-slit_experiment#Relational_interpretation)).
Sampling CPU stack traces is no exception. In order to prevent unintended
impacts on production environments, Flame Graphs are currently available as an
opt-in feature. To enable it, you'll need to set [`rest.flamegraph.enabled:
true`]({{< ref "docs/deployment/config">}}#rest-flamegraph- [...]
+Any measurement process in and of itself inevitably affects the subject of
measurement (see the [double-split
experiment](https://en.wikipedia.org/wiki/Double-slit_experiment#Relational_interpretation)).
Sampling CPU stack traces is no exception. In order to prevent unintended
impacts on production environments, Flame Graphs are currently available as an
opt-in feature. To enable it, you'll need to set [`rest.flamegraph.enabled:
true`]({{< ref "docs/deployment/config">}}#rest-flamegraph- [...]
{{< /hint >}}
diff --git a/docs/content.zh/docs/ops/metrics.md
b/docs/content.zh/docs/ops/metrics.md
index dba14ee4fa2..424a7d4776f 100644
--- a/docs/content.zh/docs/ops/metrics.md
+++ b/docs/content.zh/docs/ops/metrics.md
@@ -492,7 +492,7 @@ Every metric is assigned an identifier and a set of
key-value pairs under which
The identifier is based on 3 components: a user-defined name when registering
the metric, an optional user-defined scope and a system-provided scope.
For example, if `A.B` is the system scope, `C.D` the user scope and `E` the
name, then the identifier for the metric will be `A.B.C.D.E`.
-You can configure which delimiter to use for the identifier (default: `.`) by
setting the `metrics.scope.delimiter` key in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}).
+You can configure which delimiter to use for the identifier (default: `.`) by
setting the `metrics.scope.delimiter` key in [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}).
### User Scope
@@ -551,7 +551,7 @@ counter = runtime_context \
The system scope contains context information about the metric, for example in
which task it was registered or what job that task belongs to.
-Which context information should be included can be configured by setting the
following keys in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}).
+Which context information should be included can be configured by setting the
following keys in [Flink configuration file]({{< ref
"docs/deployment/config#flink-配置文件" >}}).
Each of these keys expect a format string that may contain constants (e.g.
"taskmanager") and variables (e.g. "<task_id>") which will be replaced at
runtime.
- `metrics.scope.jm`
diff --git a/docs/content.zh/docs/ops/rest_api.md
b/docs/content.zh/docs/ops/rest_api.md
index 2cd6da955e3..8d454e47e38 100644
--- a/docs/content.zh/docs/ops/rest_api.md
+++ b/docs/content.zh/docs/ops/rest_api.md
@@ -35,7 +35,7 @@ Flink 具有监控 API ，可用于查询正在运行的作业以及最近完成
## 概览
-该监控 API 由作为 `JobManager` 一部分运行的 web 服务器提供支持。默认情况下，该服务器监听 8081 端口，端口号可以通过修改
[Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file" >}})的
`rest.port` 进行配置。请注意，该监控 API 的 web 服务器和仪表盘的 web
服务器目前是相同的，因此在同一端口一起运行。不过，它们响应不同的 HTTP URL 。
+该监控 API 由作为 `JobManager` 一部分运行的 web 服务器提供支持。默认情况下，该服务器监听 8081 端口，端口号可以通过修改
[Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})的 `rest.port`
进行配置。请注意，该监控 API 的 web 服务器和仪表盘的 web 服务器目前是相同的，因此在同一端口一起运行。不过，它们响应不同的 HTTP URL 。
在多个 `JobManager` 的情况下（为了高可用），每个 JobManager 将运行自己的监控 API 实例，当 JobManager
被选举成为集群 leader 时，该实例将提供已完成和正在运行作业的相关信息。
diff --git a/docs/content.zh/docs/ops/state/state_backends.md
b/docs/content.zh/docs/ops/state/state_backends.md
index 4e4b2b08926..16102e0772b 100644
--- a/docs/content.zh/docs/ops/state/state_backends.md
+++ b/docs/content.zh/docs/ops/state/state_backends.md
@@ -114,7 +114,7 @@ EmbeddedRocksDBStateBackend 是目前唯一支持增量 CheckPoint 的 State Bac
## 设置 State Backend
-如果没有明确指定，将使用 jobmanager 做为默认的 state backend。你能在 [**Flink 配置文件**]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中为所有 Job 设置其他默认的 State
Backend。
+如果没有明确指定，将使用 jobmanager 做为默认的 state backend。你能在 [**Flink 配置文件**]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 中为所有 Job 设置其他默认的 State Backend。
每一个 Job 的 state backend 配置会覆盖默认的 state backend 配置，如下所示：
<a name="setting-the-per-job-state-backend"></a>
@@ -158,14 +158,14 @@ env =
StreamExecutionEnvironment.get_execution_environment(config)
```
{{< hint info >}}
- **注意:** 由于 RocksDB 是 Flink 默认分发包的一部分，所以如果你没在代码中使用 RocksDB，则不需要添加此依赖。而且可以在
[Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file" >}})中通过
`state.backend.type` 配置 State Backend，以及更多的 [checkpointing]({{< ref
"docs/deployment/config" >}}#checkpointing) 和 [RocksDB 特定的]({{< ref
"docs/deployment/config" >}}#rocksdb-state-backend) 参数。
+ **注意:** 由于 RocksDB 是 Flink 默认分发包的一部分，所以如果你没在代码中使用 RocksDB，则不需要添加此依赖。而且可以在
[Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})中通过
`state.backend.type` 配置 State Backend，以及更多的 [checkpointing]({{< ref
"docs/deployment/config" >}}#checkpointing) 和 [RocksDB 特定的]({{< ref
"docs/deployment/config" >}}#rocksdb-state-backend) 参数。
{{< /hint >}}
<a name="setting-default-state-backend"></a>
### 设置默认的（全局的） State Backend
-在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file" >}})
可以通过键 `state.backend.type` 设置默认的 State Backend。
+在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}}) 可以通过键
`state.backend.type` 设置默认的 State Backend。
可选值包括 *jobmanager* (HashMapStateBackend), *rocksdb*
(EmbeddedRocksDBStateBackend)，
或使用实现了 state backend 工厂 {{< gh_link
file="flink-runtime/src/main/java/org/apache/flink/runtime/state/StateBackendFactory.java"
name="StateBackendFactory" >}} 的类的全限定类名，
@@ -204,7 +204,7 @@ RocksDB 支持*增量快照*。不同于产生一个包含所有数据的全量
和基于全量快照的恢复时间相比，如果网络带宽是瓶颈，那么基于增量快照恢复可能会消耗更多时间，因为增量快照包含的 sst
文件之间可能存在数据重叠导致需要下载的数据量变大；而当 CPU 或者 IO 是瓶颈的时候，基于增量快照恢复会更快，因为从增量快照恢复不需要解析 Flink
的统一快照格式来重建本地的 RocksDB 数据表，而是可以直接基于 sst 文件加载。
虽然状态数据量很大时我们推荐使用增量快照，但这并不是默认的快照机制，您需要通过下述配置手动开启该功能：
- - 在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file"
>}}) 中设置：`state.backend.incremental: true` 或者
+ - 在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})
中设置：`state.backend.incremental: true` 或者
- 在代码中按照右侧方式配置（来覆盖默认配置）：`EmbeddedRocksDBStateBackend backend = new
EmbeddedRocksDBStateBackend(true);`
需要注意的是，一旦启用了增量快照，网页上展示的 `Checkpointed Data Size` 只代表增量上传的数据量，而不是一次快照的完整数据量。
@@ -270,7 +270,7 @@ Flink还提供了两个参数来控制*写路径*（MemTable）和*读路径*（
使用*预定义选项*，用户可以在每个 RocksDB 列族上应用一些预定义的配置，例如配置内存使用、线程、Compaction
设置等。目前每个算子的每个状态都在 RocksDB 中有专门的一个列族存储。
有两种方法可以选择要应用的预定义选项：
- - 通过 `state.backend.rocksdb.predefined-options` 配置项将选项名称设置进 [Flink 配置文件]({{<
ref "docs/deployment/config#flink-configuration-file" >}}) 。
+ - 通过 `state.backend.rocksdb.predefined-options` 配置项将选项名称设置进 [Flink 配置文件]({{<
ref "docs/deployment/config#flink-配置文件" >}}) 。
-
通过程序设置：`EmbeddedRocksDBStateBackend.setPredefinedOptions(PredefinedOptions.SPINNING_DISK_OPTIMIZED_HIGH_MEM)`
。
该选项的默认值是 `DEFAULT` ，对应 `PredefinedOptions.DEFAULT` 。
@@ -288,11 +288,11 @@ RocksDB State Backend 会将 [这里定义]({{< ref
"docs/deployment/config" >}}
有两种方法可以将 `RocksDBOptionsFactory` 传递给 RocksDB State Backend：
- - 通过 `state.backend.rocksdb.options-factory` 选项将工厂实现类的名称设置到[Flink 配置文件]({{<
ref "docs/deployment/config#flink-configuration-file" >}}) 。
+ - 通过 `state.backend.rocksdb.options-factory` 选项将工厂实现类的名称设置到[Flink 配置文件]({{<
ref "docs/deployment/config#flink-配置文件" >}}) 。
- 通过程序设置，例如 `EmbeddedRocksDBStateBackend.setRocksDBOptions(new
MyOptionsFactory());` 。
-<span class="label label-info">注意</span> 通过程序设置的 `RocksDBOptionsFactory` 将覆盖
[Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file" >}})
配置文件的设置，且 `RocksDBOptionsFactory` 设置的优先级高于预定义选项（`PredefinedOptions`）。
+<span class="label label-info">注意</span> 通过程序设置的 `RocksDBOptionsFactory` 将覆盖
[Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}}) 的设置，且
`RocksDBOptionsFactory` 设置的优先级高于预定义选项（`PredefinedOptions`）。
<span class="label label-info">注意</span> RocksDB是一个本地库，它直接从进程分配内存，
而不是从JVM分配内存。分配给 RocksDB 的任何内存都必须被考虑在内，通常需要将这部分内存从任务管理器（`TaskManager`）的JVM堆中减去。
diff --git a/docs/content.zh/docs/ops/state/task_failure_recovery.md
b/docs/content.zh/docs/ops/state/task_failure_recovery.md
index 50a3c7d6da8..b7e9dba546c 100644
--- a/docs/content.zh/docs/ops/state/task_failure_recovery.md
+++ b/docs/content.zh/docs/ops/state/task_failure_recovery.md
@@ -38,7 +38,7 @@ Flink 通过重启策略和故障恢复策略来控制 Task 重启：重启策
Flink 作业如果没有定义重启策略，则会遵循集群启动时加载的默认重启策略。
如果提交作业时设置了重启策略，该策略将覆盖掉集群的默认策略。
-通过 Flink 的配置文件 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 来设置默认的重启策略。配置参数
*restart-strategy.type* 定义了采取何种策略。
+通过 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})
来设置默认的重启策略。配置参数 *restart-strategy.type* 定义了采取何种策略。
如果没有启用 checkpoint，就采用“不重启”策略。如果启用了 checkpoint 且没有配置重启策略，那么就采用固定延时重启策略，
此时最大尝试重启次数由 `Integer.MAX_VALUE` 参数设置。下表列出了可用的重启策略和与其对应的配置值。
@@ -93,7 +93,7 @@ env =
StreamExecutionEnvironment.get_execution_environment(config)
如果尝试超过了给定的最大次数，作业将最终失败。
在连续的两次重启尝试之间，重启策略等待一段固定长度的时间。
-通过在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file"
>}}) 中设置如下配置参数，默认启用此策略。
+通过在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})
中设置如下配置参数，默认启用此策略。
```yaml
restart-strategy.type: fixed-delay
@@ -205,7 +205,7 @@ Python API 不支持。
故障率重启策略在故障发生之后重启作业，但是当**故障率**（每个时间间隔发生故障的次数）超过设定的限制时，作业会最终失败。
在连续的两次重启尝试之间，重启策略等待一段固定长度的时间。
-通过在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-configuration-file"
>}}) 中设置如下配置参数，默认启用此策略。
+通过在 [Flink 配置文件]({{< ref "docs/deployment/config#flink-配置文件" >}})
中设置如下配置参数，默认启用此策略。
```yaml
restart-strategy.type: failure-rate
@@ -298,7 +298,7 @@ env =
StreamExecutionEnvironment.get_execution_environment(config)
## Failover Strategies
-Flink 支持多种不同的故障恢复策略，该策略需要通过 Flink 配置文件 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) 中的
*jobmanager.execution.failover-strategy*
+Flink 支持多种不同的故障恢复策略，该策略需要通过 [Flink 配置文件]({{< ref
"docs/deployment/config#flink-配置文件" >}}) 中的
*jobmanager.execution.failover-strategy*
配置项进行配置。
<table class="table table-bordered">
diff --git a/docs/content.zh/docs/try-flink/flink-operations-playground.md
b/docs/content.zh/docs/try-flink/flink-operations-playground.md
index cdc73428f73..199831654f8 100644
--- a/docs/content.zh/docs/try-flink/flink-operations-playground.md
+++ b/docs/content.zh/docs/try-flink/flink-operations-playground.md
@@ -377,8 +377,8 @@ Suspending job "<job-id>" with a savepoint.
Suspended job "<job-id>" with a savepoint.
```
-Savepoint 已保存在 `state.savepoints.dir` 指定的路径中，该配置在 [*Flink 配置文件*]({{< ref
"docs/deployment/config#flink-configuration-file" >}})
-中定义，[*Flink 配置文件*]({{< ref "docs/deployment/config#flink-configuration-file"
>}}) 挂载在本机的 */tmp/flink-savepoints-directory/* 目录下。
+Savepoint 已保存在 `state.savepoints.dir` 指定的路径中，该配置在 [*Flink 配置文件*]({{< ref
"docs/deployment/config#flink-配置文件" >}})
+中定义，[*Flink 配置文件*]({{< ref "docs/deployment/config#flink-配置文件" >}}) 挂载在本机的
*/tmp/flink-savepoints-directory/* 目录下。
在下一步操作中我们会用到这个 Savepoint 路径，如果我们是通过 REST API 操作的，
那么 Savepoint 路径会随着响应结果一起返回，我们可以直接查看文件系统来确认 Savepoint 保存情况。
diff --git
a/docs/content/docs/deployment/resource-providers/standalone/docker.md
b/docs/content/docs/deployment/resource-providers/standalone/docker.md
index e3eca1b1cfb..a6614c7e111 100644
--- a/docs/content/docs/deployment/resource-providers/standalone/docker.md
+++ b/docs/content/docs/deployment/resource-providers/standalone/docker.md
@@ -533,7 +533,7 @@ To provide a custom location for the Flink configuration
files, you can
{{< hint info >}}
The mounted volume must contain all necessary configuration files.
-The [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) file must have write
permission so that the Docker entry point script can modify it in certain cases.
+The [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) must have write
permission so that the Docker entry point script can modify it in certain cases.
{{< /hint >}}
### Using Filesystem Plugins
diff --git a/docs/content/docs/deployment/resource-providers/yarn.md
b/docs/content/docs/deployment/resource-providers/yarn.md
index f0feaf3a8bb..7c48d526f8c 100644
--- a/docs/content/docs/deployment/resource-providers/yarn.md
+++ b/docs/content/docs/deployment/resource-providers/yarn.md
@@ -151,7 +151,7 @@ You can **re-attach to a YARN session** using the following
command:
./bin/yarn-session.sh -id application_XXXX_YY
```
-Besides passing [configuration]({{< ref "docs/deployment/config" >}}) via the
[Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) file, you can also pass
any configuration at submission time to the `./bin/yarn-session.sh` client
using `-Dkey=value` arguments.
+Besides passing [configuration]({{< ref "docs/deployment/config" >}}) via the
[Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}), you can also pass any
configuration at submission time to the `./bin/yarn-session.sh` client using
`-Dkey=value` arguments.
The YARN session client also has a few "shortcut arguments" for commonly used
settings. They can be listed with `./bin/yarn-session.sh -h`.
diff --git a/docs/content/docs/dev/datastream/fault-tolerance/state_backends.md
b/docs/content/docs/dev/datastream/fault-tolerance/state_backends.md
index f379efc5ce0..254dab00c60 100644
--- a/docs/content/docs/dev/datastream/fault-tolerance/state_backends.md
+++ b/docs/content/docs/dev/datastream/fault-tolerance/state_backends.md
@@ -28,7 +28,7 @@ under the License.
Flink provides different state backends that specify how and where state is
stored.
-State can be located on Java’s heap or off-heap. Depending on your state
backend, Flink can also manage the state for the application, meaning Flink
deals with the memory management (possibly spilling to disk if necessary) to
allow applications to hold very large state. By default, the configuration file
[*Flink configuration file*]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) determines the state
backend for all Flink jobs.
+State can be located on Java’s heap or off-heap. Depending on your state
backend, Flink can also manage the state for the application, meaning Flink
deals with the memory management (possibly spilling to disk if necessary) to
allow applications to hold very large state. By default, the [*Flink
configuration file*]({{< ref "docs/deployment/config#flink-configuration-file"
>}}) determines the state backend for all Flink jobs.
However, the default state backend can be overridden on a per-job basis, as
shown below.
diff --git a/docs/content/docs/dev/table/sqlClient.md
b/docs/content/docs/dev/table/sqlClient.md
index 95e17101144..131d1914c10 100644
--- a/docs/content/docs/dev/table/sqlClient.md
+++ b/docs/content/docs/dev/table/sqlClient.md
@@ -84,7 +84,7 @@ Cache-Control: no-cache
EOF)
```
-By default, the SQL Client will use the truststore configured using the
`security.ssl.rest.truststore` and `security.ssl.rest.truststore-password`
properties in the [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) file on the SQL client
side. If these properties aren't explicitly configured, the client will use the
default certificate stores provided by the JDK.
+By default, the SQL Client will use the truststore configured using the
`security.ssl.rest.truststore` and `security.ssl.rest.truststore-password`
properties in the [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}) on the SQL client side.
If these properties aren't explicitly configured, the client will use the
default certificate stores provided by the JDK.
<span class="label label-danger">Note</span> SQL Client only supports
connecting to the [REST Endpoint]({{< ref "docs/dev/table/sql-gateway/rest"
>}}#rest-api) since version v2.
diff --git a/docs/content/docs/ops/state/task_failure_recovery.md
b/docs/content/docs/ops/state/task_failure_recovery.md
index 911796000f2..094667fea29 100644
--- a/docs/content/docs/ops/state/task_failure_recovery.md
+++ b/docs/content/docs/ops/state/task_failure_recovery.md
@@ -39,7 +39,7 @@ Failover strategies decide which tasks should be restarted to
recover the job.
The cluster can be started with a default restart strategy which is always
used when no job specific restart strategy has been defined.
In case that the job is submitted with a restart strategy, this strategy
overrides the cluster's default setting.
-The default restart strategy is set via Flink's configuration file [Flink
configuration file]({{< ref "docs/deployment/config#flink-configuration-file"
>}}).
+The default restart strategy is set via [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}).
The configuration parameter *restart-strategy.type* defines which strategy is
taken.
If checkpointing is not enabled, the "no restart" strategy is used.
If checkpointing is activated and the restart strategy has not been
configured, the fixed-delay strategy is used with
@@ -301,7 +301,7 @@ By default, a fixed delay restart strategy is chosen if
there is no other restar
## Failover Strategies
Flink supports different failover strategies which can be configured via the
configuration parameter
-*jobmanager.execution.failover-strategy* in Flink's configuration file [Flink
configuration file]({{< ref "docs/deployment/config#flink-configuration-file"
>}}).
+*jobmanager.execution.failover-strategy* in [Flink configuration file]({{< ref
"docs/deployment/config#flink-configuration-file" >}}).
<table class="table table-bordered">
<thead>
