MrWhiteSike commented on a change in pull request #13812: URL: https://github.com/apache/flink/pull/13812#discussion_r803634749
########## File path: docs/ops/deployment/docker.zh.md ########## @@ -23,72 +23,71 @@ specific language governing permissions and limitations under the License. --> -[Docker](https://www.docker.com) is a popular container runtime. -There are Docker images for Apache Flink available [on Docker Hub](https://hub.docker.com/_/flink). -You can use the docker images to deploy a *Session* or *Job cluster* in a containerized environment, e.g., -[standalone Kubernetes](kubernetes.html) or [native Kubernetes](native_kubernetes.html). +[Docker](https://www.docker.com) 是一种流行的容器引擎。 +可以在 [Docker Hub](https://hub.docker.com/_/flink) 上获取 Apache Flink 可用的 Docker 镜像。 +你可以使用 docker 镜像在容器环境中，例如 [standalone Kubernetes](kubernetes.html) 或 [native Kubernetes](native_kubernetes.html) 中部署 *Session 集群* 或 *Job 集群*。 Review comment: ```suggestion 在容器环境中你可以使用 docker 镜像，例如 [standalone Kubernetes](kubernetes.html) 或 [native Kubernetes](native_kubernetes.html) 中部署 *Session 集群* 或 *Job 集群*。 ``` ########## File path: docs/ops/deployment/docker.zh.md ########## @@ -23,72 +23,71 @@ specific language governing permissions and limitations under the License. --> -[Docker](https://www.docker.com) is a popular container runtime. -There are Docker images for Apache Flink available [on Docker Hub](https://hub.docker.com/_/flink). -You can use the docker images to deploy a *Session* or *Job cluster* in a containerized environment, e.g., -[standalone Kubernetes](kubernetes.html) or [native Kubernetes](native_kubernetes.html). +[Docker](https://www.docker.com) 是一种流行的容器引擎。 +可以在 [Docker Hub](https://hub.docker.com/_/flink) 上获取 Apache Flink 可用的 Docker 镜像。 +你可以使用 docker 镜像在容器环境中，例如 [standalone Kubernetes](kubernetes.html) 或 [native Kubernetes](native_kubernetes.html) 中部署 *Session 集群* 或 *Job 集群*。 * This will be replaced by the TOC {:toc} -## Docker Hub Flink images +## Docker Hub 里的 Flink 镜像 -The [Flink Docker repository](https://hub.docker.com/_/flink/) is hosted on -Docker Hub and serves images of Flink version 1.2.1 and later. +[Flink Docker](https://hub.docker.com/_/flink/) 仓库托管在 Docker Hub，并提供 Flink 1.2.1 及更高版本的镜像。 -### Image tags +<a name="image-tags"></a> -Images for each supported combination of Flink and Scala versions are available, and -[tag aliases](https://hub.docker.com/_/flink?tab=tags) are provided for convenience. +### 镜像标记 -For example, you can use the following aliases: +任意受支持的 Flink 和 Scala 版本组合的镜像均是可用的，并提供 [tag aliases](https://hub.docker.com/_/flink?tab=tags) 以方便使用。 + +例如，你可以使用以下标记: * `flink:latest` → `flink:<latest-flink>-scala_<latest-scala>` * `flink:1.11` → `flink:1.11.<latest-flink-1.11>-scala_2.11` -<span class="label label-info">Note</span>It is recommended to always use an explicit version tag of the docker image that specifies both the needed Flink and Scala -versions (for example `flink:1.11-scala_2.12`). -This will avoid some class conflicts that can occur if the Flink and/or Scala versions used in the application are different -from the versions provided by the docker image. +<span class="label label-info">注意</span> 建议始终使用 docker 镜像的显式版本标记，指定所需的 Flink 和 Scala 版本号(例如 `flink:1.11-scala_2.12`)。 +避免当应用程序中使用的 Flink 和(或) Scala 版本与 docker 镜像提供的版本不同时可能引发的类冲突。 + +<span class="label label-info">注意</span> 在 Flink 1.5 版本之前，Hadoop 依赖总是和 Flink 捆绑在一起。 +你可以看到某些标签包含了 Hadoop 的版本(例如: `-hadoop28`)。 +从 Flink 1.5 版本开始，省略 Hadoop 版本的镜像标记对应 Flink 的 Hadoop-free 版本，即不包含捆绑的 Hadoop 发行版。 Review comment: ```suggestion 从 Flink 1.5 版本开始，省略 Hadoop 版本的镜像标记与之相对应 Flink 的是 Hadoop-free 版本，即不捆绑 Hadoop 的发行版。 ``` ########## File path: docs/ops/deployment/docker.zh.md ########## @@ -111,25 +110,25 @@ docker run \ flink:{% if site.is_stable %}{{site.version}}-scala{{site.scala_version_suffix}}{% else %}latest{% endif %} taskmanager ``` +<a name="start-a-job-cluster"></a> -### Start a Job Cluster +### 启动 Job 集群 -A *Flink Job cluster* is a dedicated cluster which runs a single job. -In this case, you deploy the cluster with the job as one step, thus, there is no extra job submission needed. +*Flink Job 集群*是运行单个作业的专用集群。 +这种情况下，包含作业的集群部署将在一个步骤中完成，因此不需要额外的作业提交过程。 -The *job artifacts* are included into the class path of Flink's JVM process within the container and consist of: -* your job jar, which you would normally submit to a *Session cluster* and -* all other necessary dependencies or resources, not included into Flink. +*job artifacts* 包含在容器内 Flink 的 JVM 进程的类路径中，包括： +* 你的作业 jar 包，该 jar 包通常会提交给 *Session 集群* +* 所有未包含在 Flink 中的必要依赖和资源。 Review comment: ```suggestion * 并且包含了所有未包含在 Flink 中的必要依赖和资源。 ``` ########## File path: docs/ops/deployment/docker.zh.md ########## @@ -23,72 +23,71 @@ specific language governing permissions and limitations under the License. --> -[Docker](https://www.docker.com) is a popular container runtime. -There are Docker images for Apache Flink available [on Docker Hub](https://hub.docker.com/_/flink). -You can use the docker images to deploy a *Session* or *Job cluster* in a containerized environment, e.g., -[standalone Kubernetes](kubernetes.html) or [native Kubernetes](native_kubernetes.html). +[Docker](https://www.docker.com) 是一种流行的容器引擎。 +可以在 [Docker Hub](https://hub.docker.com/_/flink) 上获取 Apache Flink 可用的 Docker 镜像。 +你可以使用 docker 镜像在容器环境中，例如 [standalone Kubernetes](kubernetes.html) 或 [native Kubernetes](native_kubernetes.html) 中部署 *Session 集群* 或 *Job 集群*。 * This will be replaced by the TOC {:toc} -## Docker Hub Flink images +## Docker Hub 里的 Flink 镜像 -The [Flink Docker repository](https://hub.docker.com/_/flink/) is hosted on -Docker Hub and serves images of Flink version 1.2.1 and later. +[Flink Docker](https://hub.docker.com/_/flink/) 仓库托管在 Docker Hub，并提供 Flink 1.2.1 及更高版本的镜像。 -### Image tags +<a name="image-tags"></a> -Images for each supported combination of Flink and Scala versions are available, and -[tag aliases](https://hub.docker.com/_/flink?tab=tags) are provided for convenience. +### 镜像标记 -For example, you can use the following aliases: +任意受支持的 Flink 和 Scala 版本组合的镜像均是可用的，并提供 [tag aliases](https://hub.docker.com/_/flink?tab=tags) 以方便使用。 + +例如，你可以使用以下标记: * `flink:latest` → `flink:<latest-flink>-scala_<latest-scala>` * `flink:1.11` → `flink:1.11.<latest-flink-1.11>-scala_2.11` -<span class="label label-info">Note</span>It is recommended to always use an explicit version tag of the docker image that specifies both the needed Flink and Scala -versions (for example `flink:1.11-scala_2.12`). -This will avoid some class conflicts that can occur if the Flink and/or Scala versions used in the application are different -from the versions provided by the docker image. +<span class="label label-info">注意</span> 建议始终使用 docker 镜像的显式版本标记，指定所需的 Flink 和 Scala 版本号(例如 `flink:1.11-scala_2.12`)。 +避免当应用程序中使用的 Flink 和(或) Scala 版本与 docker 镜像提供的版本不同时可能引发的类冲突。 + +<span class="label label-info">注意</span> 在 Flink 1.5 版本之前，Hadoop 依赖总是和 Flink 捆绑在一起。 +你可以看到某些标签包含了 Hadoop 的版本(例如: `-hadoop28`)。 +从 Flink 1.5 版本开始，省略 Hadoop 版本的镜像标记对应 Flink 的 Hadoop-free 版本，即不包含捆绑的 Hadoop 发行版。 + +<a name="how-to-run-a-flink-image"></a> -<span class="label label-info">Note</span> Prior to Flink 1.5 version, Hadoop dependencies were always bundled with Flink. -You can see that certain tags include the version of Hadoop, e.g. (e.g. `-hadoop28`). -Beginning with Flink 1.5, image tags that omit the Hadoop version correspond to Hadoop-free releases of Flink -that do not include a bundled Hadoop distribution. +## 如何运行 Flink 镜像 -## How to run a Flink image +Flink 镜像包含具有默认配置的常规 Flink 发行版和标准的 entry point 脚本。 +你可以在如下模式下运行它的 entry point: +* [Session 集群](#start-a-session-cluster) 的 [JobManager]({% link concepts/glossary.zh.md %}#flink-jobmanager) +* [Job 集群](#start-a-job-cluster) 的 [JobManager]({% link concepts/glossary.zh.md %}#flink-jobmanager) +* 任意集群的 [TaskManager]({% link concepts/glossary.zh.md %}#flink-taskmanager) -The Flink image contains a regular Flink distribution with its default configuration and a standard entry point script. -You can run its entry point in the following modes: -* [JobManager]({% link concepts/glossary.zh.md %}#flink-jobmanager) for [a Session cluster](#start-a-session-cluster) -* [JobManager]({% link concepts/glossary.zh.md %}#flink-jobmanager) for [a Job cluster](#start-a-job-cluster) -* [TaskManager]({% link concepts/glossary.zh.md %}#flink-taskmanager) for any cluster +这允许你在任何容器环境中部署一个独立集群 (Session 或 Job)，例如: +* 本地 Docker 环境中手动部署 +* [Kubernetes cluster](kubernetes.html) +* [Docker Compose](#flink-with-docker-compose) +* [Docker swarm](#flink-with-docker-swarm) -This allows you to deploy a standalone cluster (Session or Job) in any containerised environment, for example: -* manually in a local Docker setup, -* [in a Kubernetes cluster](kubernetes.html), -* [with Docker Compose](#flink-with-docker-compose), -* [with Docker swarm](#flink-with-docker-swarm). +<span class="label label-info">注意</span> [The native Kubernetes](native_kubernetes.html) 默认情况下也运行相同的镜像，并按需部署 *TaskManagers* ，因此你不必手动执行。 -<span class="label label-info">Note</span> [The native Kubernetes](native_kubernetes.html) also runs the same image by default -and deploys *TaskManagers* on demand so that you do not have to do it manually. +接下来的章节将描述如何启动一个用于多种目的的 Flink Docker 容器。 -The next chapters describe how to start a single Flink Docker container for various purposes. +一旦你在 Docker 上启动了 Flink，你可以通过访问 Flink 的前端页面 [localhost:8081](http://localhost:8081/#/overview)，或者通过 `./bin/flink run ./examples/streaming/TopSpeedWindowing.jar` 命令来提交作业。 -Once you've started Flink on Docker, you can access the Flink Webfrontend on [localhost:8081](http://localhost:8081/#/overview) or submit jobs like this `./bin/flink run ./examples/streaming/TopSpeedWindowing.jar`. +我们建议使用 [Docker Compose](docker.html#session-cluster-with-docker-compose) 或 [Docker Swarm](docker.html#session-cluster-with-docker-swarm) 将 Flink 部署为 Session 集群，以简化系统配置。 -We recommend using [Docker Compose](docker.html#session-cluster-with-docker-compose) or [Docker Swarm](docker.html#session-cluster-with-docker-swarm) for deploying Flink as a Session Cluster to ease system configuration. +<a name="start-a-session-cluster"></a> -### Start a Session Cluster +### 启动 Session 集群 -A *Flink Session cluster* can be used to run multiple jobs. Each job needs to be submitted to the cluster after it has been deployed. -To deploy a *Flink Session cluster* with Docker, you need to start a *JobManager* container. To enable communication between the containers, we first set a required Flink configuration property and create a network: +*Flink Session 集群* 可用于运行多个作业。每个作业都必须在集群部署之后才可以提交。 Review comment: ```suggestion *Flink Session 集群* 可运行多个作业。每个作业都必须在集群部署之后才可以提交。 ``` ########## File path: docs/ops/deployment/docker.zh.md ########## @@ -23,72 +23,71 @@ specific language governing permissions and limitations under the License. --> -[Docker](https://www.docker.com) is a popular container runtime. -There are Docker images for Apache Flink available [on Docker Hub](https://hub.docker.com/_/flink). -You can use the docker images to deploy a *Session* or *Job cluster* in a containerized environment, e.g., -[standalone Kubernetes](kubernetes.html) or [native Kubernetes](native_kubernetes.html). +[Docker](https://www.docker.com) 是一种流行的容器引擎。 +可以在 [Docker Hub](https://hub.docker.com/_/flink) 上获取 Apache Flink 可用的 Docker 镜像。 +你可以使用 docker 镜像在容器环境中，例如 [standalone Kubernetes](kubernetes.html) 或 [native Kubernetes](native_kubernetes.html) 中部署 *Session 集群* 或 *Job 集群*。 * This will be replaced by the TOC {:toc} -## Docker Hub Flink images +## Docker Hub 里的 Flink 镜像 -The [Flink Docker repository](https://hub.docker.com/_/flink/) is hosted on -Docker Hub and serves images of Flink version 1.2.1 and later. +[Flink Docker](https://hub.docker.com/_/flink/) 仓库托管在 Docker Hub，并提供 Flink 1.2.1 及更高版本的镜像。 -### Image tags +<a name="image-tags"></a> -Images for each supported combination of Flink and Scala versions are available, and -[tag aliases](https://hub.docker.com/_/flink?tab=tags) are provided for convenience. +### 镜像标记 -For example, you can use the following aliases: +任意受支持的 Flink 和 Scala 版本组合的镜像均是可用的，并提供 [tag aliases](https://hub.docker.com/_/flink?tab=tags) 以方便使用。 Review comment: ```suggestion 任意支持 Flink 和 Scala 版本组合的镜像均是可用的，并提供 [tag aliases](https://hub.docker.com/_/flink?tab=tags) 以方便使用。 ``` ########## File path: docs/ops/deployment/docker.zh.md ########## @@ -111,25 +110,25 @@ docker run \ flink:{% if site.is_stable %}{{site.version}}-scala{{site.scala_version_suffix}}{% else %}latest{% endif %} taskmanager ``` +<a name="start-a-job-cluster"></a> -### Start a Job Cluster +### 启动 Job 集群 -A *Flink Job cluster* is a dedicated cluster which runs a single job. -In this case, you deploy the cluster with the job as one step, thus, there is no extra job submission needed. +*Flink Job 集群*是运行单个作业的专用集群。 +这种情况下，包含作业的集群部署将在一个步骤中完成，因此不需要额外的作业提交过程。 -The *job artifacts* are included into the class path of Flink's JVM process within the container and consist of: -* your job jar, which you would normally submit to a *Session cluster* and -* all other necessary dependencies or resources, not included into Flink. +*job artifacts* 包含在容器内 Flink 的 JVM 进程的类路径中，包括： +* 你的作业 jar 包，该 jar 包通常会提交给 *Session 集群* Review comment: ```suggestion * 你的作业 jar 包通常会提交给 *Session 集群*， ``` -- 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]
