This is an automated email from the ASF dual-hosted git repository.
snuyanzin 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 17216cee20f [hotfix][docs] Fix duplicate word typos in documentation
17216cee20f is described below
commit 17216cee20f731a258d96fcee3719b7f737b0d4f
Author: jhanishant260 <[email protected]>
AuthorDate: Tue May 26 03:41:35 2026 +0530
[hotfix][docs] Fix duplicate word typos in documentation
---
docs/content.zh/docs/sql/reference/ddl/create.md | 2 +-
docs/content/docs/ops/batch/batch_shuffle.md | 4 ++--
docs/content/docs/sql/reference/ddl/create.md | 2 +-
3 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/docs/content.zh/docs/sql/reference/ddl/create.md
b/docs/content.zh/docs/sql/reference/ddl/create.md
index e6914b0a417..28e6411e0de 100644
--- a/docs/content.zh/docs/sql/reference/ddl/create.md
+++ b/docs/content.zh/docs/sql/reference/ddl/create.md
@@ -236,7 +236,7 @@ CREATE TABLE MyTable (
Metadata columns are an extension to the SQL standard and allow to access
connector and/or format specific
fields for every row of a table. A metadata column is indicated by the
`METADATA` keyword. For example,
-a metadata column can be be used to read and write the timestamp from and to
Kafka records for time-based
+a metadata column can be used to read and write the timestamp from and to
Kafka records for time-based
operations. The [connector and format documentation]({{< ref
"docs/connectors/table/overview" >}}) lists the
available metadata fields for every component. However, declaring a metadata
column in a table's schema
is optional.
diff --git a/docs/content/docs/ops/batch/batch_shuffle.md
b/docs/content/docs/ops/batch/batch_shuffle.md
index b28add22c46..bb6f99ac482 100644
--- a/docs/content/docs/ops/batch/batch_shuffle.md
+++ b/docs/content/docs/ops/batch/batch_shuffle.md
@@ -173,7 +173,7 @@ Here are some exceptions you may encounter (rarely) and the
corresponding soluti
| :--------- | :------------------ |
| Insufficient number of network buffers | This means the amount of network
memory is not enough to run the target job and you need to increase the total
network memory size. Note that since 1.15, `Sort Shuffle` has become the
default blocking shuffle implementation and for some cases, it may need more
network memory than before, which means there is a small possibility that your
batch jobs may suffer from this issue after upgrading to 1.15. If this is the
case, you just need to increase [...]
| Too many open files | This means that the file descriptors is not enough. If
you are using `Hash Shuffle`, please switch to `Sort Shuffle`. If you are
already using `Sort Shuffle`, please consider increasing the system limit for
file descriptor and check if the user code consumes too many file descriptors. |
-| Connection reset by peer | This usually means that the network is unstable
or or under heavy burden. Other issues like SSL handshake timeout mentioned
above may also cause this problem. If you are using `Hash Shuffle`, please
switch to `Sort Shuffle`. If you are already using `Sort Shuffle`, increasing
the [network backlog]({{< ref "docs/deployment/config"
>}}#taskmanager-network-netty-server-backlog) may help. |
+| Connection reset by peer | This usually means that the network is unstable
or under heavy burden. Other issues like SSL handshake timeout mentioned above
may also cause this problem. If you are using `Hash Shuffle`, please switch to
`Sort Shuffle`. If you are already using `Sort Shuffle`, increasing the
[network backlog]({{< ref "docs/deployment/config"
>}}#taskmanager-network-netty-server-backlog) may help. |
| Network connection timeout | This usually means that the network is unstable
or under heavy burden and increasing the [network connection timeout]({{< ref
"docs/deployment/config"
>}}#taskmanager-network-netty-client-connectTimeoutSec) or enable [connection
retry]({{< ref "docs/deployment/config" >}}#taskmanager-network-retries) may
help. |
| Socket read/write timeout | This may indicate that the network is slow or
under heavy burden and increasing the [network send/receive buffer size]({{<
ref "docs/deployment/config"
>}}#taskmanager-network-netty-sendReceiveBufferSize) may help. If the job is
running in Kubernetes environment, using [host network]({{< ref
"docs/deployment/config" >}}#kubernetes-hostnetwork-enabled) may also help. |
| Read buffer request timeout | This can happen only when you are using `Sort
Shuffle` and it means a fierce contention of the shuffle read memory. To solve
the issue, you can increase
[taskmanager.memory.framework.off-heap.batch-shuffle.size]({{< ref
"docs/deployment/config"
>}}#taskmanager-memory-framework-off-heap-batch-shuffle-size) together with
[taskmanager.memory.framework.off-heap.size]({{< ref "docs/deployment/config"
>}}#taskmanager-memory-framework-off-heap-size). |
@@ -188,7 +188,7 @@ Here are some exceptions you may encounter (rarely) and the
corresponding soluti
| Exceptions | Potential Solutions
[...]
|:--------------------------------------------|:------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[...]
| Insufficient number of network buffers | This means the amount of
network memory is not enough to run the target job and you need to increase the
total network memory size.
[...]
-| Connection reset by peer | This usually means that the
network is unstable or or under heavy burden. Other issues like SSL handshake
timeout may also cause this problem. Increasing the [network backlog]({{< ref
"docs/deployment/config" >}}#taskmanager-network-netty-server-backlog) may
help.
[...]
+| Connection reset by peer | This usually means that the
network is unstable or under heavy burden. Other issues like SSL handshake
timeout may also cause this problem. Increasing the [network backlog]({{< ref
"docs/deployment/config" >}}#taskmanager-network-netty-server-backlog) may
help.
[...]
| Network connection timeout | This usually means that the
network is unstable or under heavy burden and increasing the [network
connection timeout]({{< ref "docs/deployment/config"
>}}#taskmanager-network-netty-client-connectTimeoutSec) or enable [connection
retry]({{< ref "docs/deployment/config" >}}#taskmanager-network-retries) may
help.
[...]
| Socket read/write timeout | This may indicate that the
network is slow or under heavy burden and increasing the [network send/receive
buffer size]({{< ref "docs/deployment/config"
>}}#taskmanager-network-netty-sendReceiveBufferSize) may help. If the job is
running in Kubernetes environment, using [host network]({{< ref
"docs/deployment/config" >}}#kubernetes-hostnetwork-enabled) may also help.
[...]
| Read buffer request timeout | This means a fierce contention
of the shuffle read memory. To solve the issue, you can increase
[taskmanager.memory.framework.off-heap.batch-shuffle.size]({{< ref
"docs/deployment/config"
>}}#taskmanager-memory-framework-off-heap-batch-shuffle-size) together with
[taskmanager.memory.framework.off-heap.size]({{< ref "docs/deployment/config"
>}}#taskmanager-memory-framework-off-heap-size).
[...]
diff --git a/docs/content/docs/sql/reference/ddl/create.md
b/docs/content/docs/sql/reference/ddl/create.md
index 3728d0038ca..0a1c711f2a6 100644
--- a/docs/content/docs/sql/reference/ddl/create.md
+++ b/docs/content/docs/sql/reference/ddl/create.md
@@ -232,7 +232,7 @@ CREATE TABLE MyTable (
Metadata columns are an extension to the SQL standard and allow to access
connector and/or format specific
fields for every row of a table. A metadata column is indicated by the
`METADATA` keyword. For example,
-a metadata column can be be used to read and write the timestamp from and to
Kafka records for time-based
+a metadata column can be used to read and write the timestamp from and to
Kafka records for time-based
operations. The [connector and format documentation]({{< ref
"docs/connectors/table/overview" >}}) lists the
available metadata fields for every component. However, declaring a metadata
column in a table's schema
is optional.
