liuzhuang2017 commented on code in PR #19413:
URL: https://github.com/apache/flink/pull/19413#discussion_r847981768
##########
docs/content.zh/docs/ops/state/large_state_tuning.md:
##########
@@ -166,149 +125,101 @@ public class MyOptionsFactory implements
ConfigurableRocksDBOptionsFactory {
}
```
-## Capacity Planning
-
-This section discusses how to decide how many resources should be used for a
Flink job to run reliably.
-The basic rules of thumb for capacity planning are:
-
- - Normal operation should have enough capacity to not operate under constant
*back pressure*.
- See [back pressure monitoring]({{< ref "docs/ops/monitoring/back_pressure"
>}}) for details on how to check whether the application runs under back
pressure.
-
- - Provision some extra resources on top of the resources needed to run the
program back-pressure-free during failure-free time.
- These resources are needed to "catch up" with the input data that
accumulated during the time the application
- was recovering.
- How much that should be depends on how long recovery operations usually
take (which depends on the size of the state
- that needs to be loaded into the new TaskManagers on a failover) and how
fast the scenario requires failures to recover.
-
- *Important*: The base line should to be established with checkpointing
activated, because checkpointing ties up
- some amount of resources (such as network bandwidth).
-
- - Temporary back pressure is usually okay, and an essential part of
execution flow control during load spikes,
- during catch-up phases, or when external systems (that are written to in a
sink) exhibit temporary slowdown.
+## 容量规划
+本节讨论如何确定 Flink 作业应该使用多少资源才能可靠地运行。
+容量规划的基本经验法则是：
+ - 正常运行应该有足够的能力在恒定的*反压*下运行。
Review Comment:
这里我提了一个 hotfix pr，在 https://github.com/apache/flink/pull/19429，帮忙看看，感谢。
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
