caozhen1937 commented on a change in pull request #14088: URL: https://github.com/apache/flink/pull/14088#discussion_r533884649
########## File path: docs/concepts/flink-architecture.zh.md ########## @@ -24,229 +24,109 @@ specific language governing permissions and limitations under the License. --> -Flink is a distributed system and requires effective allocation and management -of compute resources in order to execute streaming applications. It integrates -with all common cluster resource managers such as [Hadoop -YARN](https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/YARN.html), -[Apache Mesos](https://mesos.apache.org/) and -[Kubernetes](https://kubernetes.io/), but can also be set up to run as a -standalone cluster or even as a library. +Flink 是一个分布式系统，需要有效分配和管理计算资源才能执行流应用程序。它集成了所有常见的集群资源管理器，例如[Hadoop YARN](https://hadoop.apache.org/docs/stable/hadoop-yarn/hadoop-yarn-site/YARN.html)、[Apache Mesos](https://mesos.apache.org/)和[Kubernetes](https://kubernetes.io/)，但也可以设置作为独立集群甚至库运行。 -This section contains an overview of Flink’s architecture and describes how its -main components interact to execute applications and recover from failures. +本节概述了 Flink 架构，并且描述了其主要组件如何交互以执行应用程序和从故障中恢复。 * This will be replaced by the TOC {:toc} -## Anatomy of a Flink Cluster +## Flink 集群剖析 -The Flink runtime consists of two types of processes: a _JobManager_ and one or more _TaskManagers_. +Flink 运行时由两种类型的进程组成：_JobManager_和一个或者多个_TaskManager_。 <img src="{% link /fig/processes.svg %}" alt="The processes involved in executing a Flink dataflow" class="offset" width="70%" /> -The *Client* is not part of the runtime and program execution, but is used to -prepare and send a dataflow to the JobManager. After that, the client can -disconnect (_detached mode_), or stay connected to receive progress reports -(_attached mode_). The client runs either as part of the Java/Scala program -that triggers the execution, or in the command line process `./bin/flink run -...`. - -The JobManager and TaskManagers can be started in various ways: directly on -the machines as a [standalone cluster]({% link -deployment/resource-providers/standalone/index.zh.md %}), in containers, or managed by resource -frameworks like [YARN]({% link deployment/resource-providers/yarn.zh.md -%}) or [Mesos]({% link deployment/resource-providers/mesos.zh.md %}). -TaskManagers connect to JobManagers, announcing themselves as available, and -are assigned work. +*Client* 不是运行时和程序执行的一部分，而是用于准备数据流并将其发送给 JobManager。之后，客户端可以断开连接（_分离模式_），或保持连接来接收进程报告（_附加模式_）。客户端可以作为触发执行 Java/Scala 程序的一部分运行，也可以在命令行进程`./bin/flink run ...`中运行。 + +可以通过各种方式启动 JobManager 和 TaskManager：直接在机器上作为[standalone 集群]({% link deployment/resource-providers/standalone/index.zh.md %})启动、在容器中启动、或者通过[YARN]({% link deployment/resource-providers/yarn.zh.md %})或[Mesos]({% link deployment/resource-providers/mesos.zh.md %})等资源框架管理启动。TaskManager 连接到 JobManagers，宣布自己可用，并被分配工作。 Review comment: 这里的 managed 是不是想表达使用资源框架 “管理并启动”？ ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
