davidradl commented on code in PR #27128: URL: https://github.com/apache/flink/pull/27128#discussion_r2498334275
########## docs/content/docs/deployment/tasks-scheduling/balanced_tasks_scheduling.md: ########## @@ -0,0 +1,118 @@ +--- +title: Balanced Tasks Scheduling +weight: 5 +type: docs + +--- +<!-- +Licensed to the Apache Software Foundation (ASF) under one +or more contributor license agreements. See the NOTICE file +distributed with this work for additional information +regarding copyright ownership. The ASF licenses this file +to you under the Apache License, Version 2.0 (the +"License"); you may not use this file except in compliance +with the License. You may obtain a copy of the License at + + http://www.apache.org/licenses/LICENSE-2.0 + +Unless required by applicable law or agreed to in writing, +software distributed under the License is distributed on an +"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +KIND, either express or implied. See the License for the +specific language governing permissions and limitations +under the License. +--> + +# Balanced Tasks Scheduling + +This page describes the background and principle of balanced tasks scheduling, +how to use it when running streaming jobs. + +## Background + +When the parallelism of all vertices within a Flink streaming job is inconsistent, Review Comment: I wonder whether we could start by saying , Flink Streaming jobs can have consistent parallelism across all vertices, , this is useful / can occur when .... Different vertices in stream job can have different parallelism across their vertices, this can occur when ...... ( for example parallelism Kafka sources may have different numbers of partition number; subsequent joining and aggregations parallelism are likely to be different again). -- 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]
