You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by GitBox <gi...@apache.org> on 2020/12/02 03:39:17 UTC

[GitHub] [flink] caozhen1937 commented on a change in pull request #14088: [FLINK-20168][docs-zh] Translate page 'Flink Architecture' into Chinese.

caozhen1937 commented on a change in pull request #14088:
URL: https://github.com/apache/flink/pull/14088#discussion_r533875476



##########
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_。

Review comment:
       这里说的是两种类型的进程,我觉得只是说明进程名称就可以,不需要指明个数,并且JobManager可能不是一个。




----------------------------------------------------------------
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:
users@infra.apache.org