From commits-return-13269-apmail-kafka-commits-archive=kafka.apache.org@kafka.apache.org Mon Dec 16 16:46:55 2019 Return-Path: X-Original-To: apmail-kafka-commits-archive@www.apache.org Delivered-To: apmail-kafka-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by minotaur.apache.org (Postfix) with SMTP id 0F614191E7 for ; Mon, 16 Dec 2019 16:46:54 +0000 (UTC) Received: (qmail 15953 invoked by uid 500); 16 Dec 2019 16:46:54 -0000 Delivered-To: apmail-kafka-commits-archive@kafka.apache.org Received: (qmail 15927 invoked by uid 500); 16 Dec 2019 16:46:54 -0000 Mailing-List: contact commits-help@kafka.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@kafka.apache.org Delivered-To: mailing list commits@kafka.apache.org Received: (qmail 15918 invoked by uid 99); 16 Dec 2019 16:46:54 -0000 Received: from ec2-52-202-80-70.compute-1.amazonaws.com (HELO gitbox.apache.org) (52.202.80.70) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Dec 2019 16:46:54 +0000 Received: by gitbox.apache.org (ASF Mail Server at gitbox.apache.org, from userid 33) id 120788D80D; Mon, 16 Dec 2019 16:46:54 +0000 (UTC) Date: Mon, 16 Dec 2019 16:46:51 +0000 To: "commits@kafka.apache.org" Subject: [kafka] branch 0.11.0 updated: port paragrpah from CP docs (#7808) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Message-ID: <157651480796.14231.11641425228102396102@gitbox.apache.org> From: bbejeck@apache.org X-Git-Host: gitbox.apache.org X-Git-Repo: kafka X-Git-Refname: refs/heads/0.11.0 X-Git-Reftype: branch X-Git-Oldrev: 54b26c0aa47184c8b31d80785d742ffa167603f0 X-Git-Newrev: 9758e2d7fdbdcd493d0892deeecabe302deade8a X-Git-Rev: 9758e2d7fdbdcd493d0892deeecabe302deade8a X-Git-NotificationType: ref_changed_plus_diff X-Git-Multimail-Version: 1.5.dev Auto-Submitted: auto-generated This is an automated email from the ASF dual-hosted git repository. bbejeck pushed a commit to branch 0.11.0 in repository https://gitbox.apache.org/repos/asf/kafka.git The following commit(s) were added to refs/heads/0.11.0 by this push: new 9758e2d port paragrpah from CP docs (#7808) 9758e2d is described below commit 9758e2d7fdbdcd493d0892deeecabe302deade8a Author: A. Sophie Blee-Goldman AuthorDate: Mon Dec 9 13:35:17 2019 -0800 port paragrpah from CP docs (#7808) The AK Streams architecture docs should explain how the maximum parallelism is determined Reviewers: Bill Bejeck --- docs/streams/architecture.html | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/streams/architecture.html b/docs/streams/architecture.html index 0dbb1dc..5b5e59e 100644 --- a/docs/streams/architecture.html +++ b/docs/streams/architecture.html @@ -53,6 +53,14 @@

+ Slightly simplified, the maximum parallelism at which your application may run is bounded by the maximum number of stream tasks, which itself is determined by + maximum number of partitions of the input topic(s) the application is reading from. For example, if your input topic has 5 partitions, then you can run up to 5 + applications instances. These instances will collaboratively process the topic’s data. If you run a larger number of app instances than partitions of the input + topic, the “excess” app instances will launch but remain idle; however, if one of the busy instances goes down, one of the idle instances will resume the former’s + work. +

+ +

It is important to understand that Kafka Streams is not a resource manager, but a library that "runs" anywhere its stream processing application runs. Multiple instances of the application are executed either on the same machine, or spread across multiple machines and tasks can be distributed automatically by the library to those running application instances. The assignment of partitions to tasks never changes; if an application instance fails, all its assigned