JimGalasyn commented on a change in pull request #9969:
URL: https://github.com/apache/kafka/pull/9969#discussion_r564106498



##########
File path: docs/streams/architecture.html
##########
@@ -110,6 +110,11 @@ <h3 class="anchor-heading"><a 
id="streams_architecture_threads" class="anchor-li
         and Kafka Streams takes care of distributing partitions amongst tasks 
that run in the application instances. You can start as many threads of the 
application
         as there are input Kafka topic partitions so that, across all running 
instances of an application, every thread (or rather, the tasks it runs) has at 
least one input partition to process.
     </p>
+    <p>
+        As of Kafka 2.8 you may scale clients much in the same way you can 
scale your application.

Review comment:
       ```suggestion
           Starting with Kafka 2.8, you can scale clients much in the same way 
that you scale your applications.
   ```

##########
File path: docs/streams/architecture.html
##########
@@ -110,6 +110,11 @@ <h3 class="anchor-heading"><a 
id="streams_architecture_threads" class="anchor-li
         and Kafka Streams takes care of distributing partitions amongst tasks 
that run in the application instances. You can start as many threads of the 
application
         as there are input Kafka topic partitions so that, across all running 
instances of an application, every thread (or rather, the tasks it runs) has at 
least one input partition to process.
     </p>
+    <p>
+        As of Kafka 2.8 you may scale clients much in the same way you can 
scale your application.
+        Simply add or remove threads and Kafka Streams will take care of 
redistributing the partitions.

Review comment:
       ```suggestion
           Simply add or remove threads, and Kafka Streams takes care of 
redistributing the partitions.
   ```

##########
File path: docs/streams/architecture.html
##########
@@ -110,6 +110,11 @@ <h3 class="anchor-heading"><a 
id="streams_architecture_threads" class="anchor-li
         and Kafka Streams takes care of distributing partitions amongst tasks 
that run in the application instances. You can start as many threads of the 
application
         as there are input Kafka topic partitions so that, across all running 
instances of an application, every thread (or rather, the tasks it runs) has at 
least one input partition to process.
     </p>
+    <p>
+        As of Kafka 2.8 you may scale clients much in the same way you can 
scale your application.
+        Simply add or remove threads and Kafka Streams will take care of 
redistributing the partitions.
+        You may also add threads to replace threads that have died removing 
the need to restart clients to recover the number of thread running.

Review comment:
       ```suggestion
           You can also add threads to replace threads that have died, removing 
the need to restart clients to recover the number of threads running.
   ```




----------------------------------------------------------------
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


Reply via email to