From 95e3aa2e91237964abf2052231927df0cb614467 Mon Sep 17 00:00:00 2001 From: Evan Zhou Date: Tue, 25 Nov 2025 16:32:36 -0800 Subject: [PATCH 1/5] add "handling crashes and failures" section to streams dev guide --- docs/streams/developer-guide/running-app.html | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) diff --git a/docs/streams/developer-guide/running-app.html b/docs/streams/developer-guide/running-app.html index a6c603f2a3c21..32292624e8506 100644 --- a/docs/streams/developer-guide/running-app.html +++ b/docs/streams/developer-guide/running-app.html @@ -46,6 +46,7 @@
  • Determining how many application instances to run
    • +
  • Handling crashes and failures
    • @@ -134,6 +135,22 @@

    Determining how many application instance
  • Data should be equally distributed across topic partitions. For example, if two topic partitions each have 1 million messages, this is better than a single partition with 2 million messages and none in the other.
  • Processing workload should be equally distributed across topic partitions. For example, if the time to process messages varies widely, then it is better to spread the processing-intensive messages across partitions rather than storing these messages within the same partition.
    • +

    +
    +

    Handling crashes and failures

    +

    It is inevitable that your application will crash or fail at some point. There are a few things you can do to reduce the likelihood of these situations. +

    +

    +

    If your Kafka Streams application does crash or fail, it will first enter the PENDING_ERROR state + to gracefully close all of its existing resources, and then transition into the ERROR state. + It is important to note that the PENDING_ERROR state is not recoverable, and only a + restart will get the application back to the RUNNING state. +

    From 94d4718209e295da16788f672d36042cdcac6281 Mon Sep 17 00:00:00 2001 From: Evan Zhou Date: Tue, 25 Nov 2025 16:34:43 -0800 Subject: [PATCH 2/5] reword for clarity --- docs/streams/developer-guide/running-app.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/streams/developer-guide/running-app.html b/docs/streams/developer-guide/running-app.html index 32292624e8506..89d0f981f1cd2 100644 --- a/docs/streams/developer-guide/running-app.html +++ b/docs/streams/developer-guide/running-app.html @@ -141,7 +141,7 @@

    Determining how many application instance

    It is inevitable that your application will crash or fail at some point. There are a few things you can do to reduce the likelihood of these situations.

    From 971e38affe418fdbd5afaa5fc073dfb9399d76a6 Mon Sep 17 00:00:00 2001 From: Evan Zhou Date: Tue, 25 Nov 2025 22:01:50 -0800 Subject: [PATCH 3/5] fix --- docs/streams/developer-guide/running-app.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/streams/developer-guide/running-app.html b/docs/streams/developer-guide/running-app.html index 89d0f981f1cd2..c52bd7d068b4e 100644 --- a/docs/streams/developer-guide/running-app.html +++ b/docs/streams/developer-guide/running-app.html @@ -147,7 +147,7 @@

    Determining how many application instance

    If your Kafka Streams application does crash or fail, it will first enter the PENDING_ERROR state - to gracefully close all of its existing resources, and then transition into the ERROR state. + to gracefully close all of its existing resources, and then transition into the ERROR state. It is important to note that the PENDING_ERROR state is not recoverable, and only a restart will get the application back to the RUNNING state.

    From cc8d5407457c8e3aca34e2c8451de8283c7daf4b Mon Sep 17 00:00:00 2001 From: Evan Zhou Date: Tue, 25 Nov 2025 22:02:43 -0800 Subject: [PATCH 4/5] reword --- docs/streams/developer-guide/running-app.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/streams/developer-guide/running-app.html b/docs/streams/developer-guide/running-app.html index c52bd7d068b4e..f30641fd34e7b 100644 --- a/docs/streams/developer-guide/running-app.html +++ b/docs/streams/developer-guide/running-app.html @@ -138,7 +138,7 @@

    Determining how many application instance

    Handling crashes and failures

    -

    It is inevitable that your application will crash or fail at some point. There are a few things you can do to reduce the likelihood of these situations. +

    There are a few things you can do to reduce the likelihood of crashes and failures of your Kafka Streams application.