From 22602b627e55a436a9b08785c4c2b49416b1dcb3 Mon Sep 17 00:00:00 2001 From: xuanhaoran Date: Sat, 30 May 2020 17:53:49 +0800 Subject: [PATCH 1/3] Update documentation for KIP-571 --- docs/streams/developer-guide/app-reset-tool.html | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/streams/developer-guide/app-reset-tool.html b/docs/streams/developer-guide/app-reset-tool.html index f42235a74cdc7..dac42950fda45 100644 --- a/docs/streams/developer-guide/app-reset-tool.html +++ b/docs/streams/developer-guide/app-reset-tool.html @@ -56,7 +56,8 @@
Prerequisites
    -

  • All instances of your application must be stopped. Otherwise, the application may enter an invalid state, crash, or produce incorrect results. You can verify whether the consumer group with ID application.id is still active by using bin/kafka-consumer-groups.

    +

  • All instances of your application must be stopped. Otherwise, the application may enter an invalid state, crash, or produce incorrect results. You can verify whether the consumer group with ID application.id is still active by using bin/kafka-consumer-groups. + When long session timeout has been configured, active members could take longer to get expired on the broker thus blocking the reset job to complete. Use the --force option could remove those left-over members immediately.

  • Use this tool with care and double-check its parameters: If you provide wrong parameter values (e.g., typos in application.id) or specify parameters inconsistently (e.g., specify the wrong input topics for the application), this tool might invalidate the application’s state or even impact other applications, consumer groups, or your Kafka topics.

    • @@ -117,6 +118,9 @@

    Step 1: Run the application reset toolStreams API enabling a user to provide StateStores with alongside Processor/Transformer logic so that they are automatically added and connected to the processor.

    +

    + We added a --force option in StreamsResetter to force remove left-over members on broker side when long session time out was configured + as per KIP-571. +

    Streams API changes in 2.5.0

    From 8df8c66ad254404b202fc4f83606030a47cbb1e7 Mon Sep 17 00:00:00 2001 From: xuanhaoran Date: Sun, 31 May 2020 22:10:11 +0800 Subject: [PATCH 3/3] fix comments --- docs/streams/developer-guide/app-reset-tool.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/streams/developer-guide/app-reset-tool.html b/docs/streams/developer-guide/app-reset-tool.html index dac42950fda45..e875a2387895e 100644 --- a/docs/streams/developer-guide/app-reset-tool.html +++ b/docs/streams/developer-guide/app-reset-tool.html @@ -57,7 +57,7 @@

    Prerequisites

    • All instances of your application must be stopped. Otherwise, the application may enter an invalid state, crash, or produce incorrect results. You can verify whether the consumer group with ID application.id is still active by using bin/kafka-consumer-groups. - When long session timeout has been configured, active members could take longer to get expired on the broker thus blocking the reset job to complete. Use the --force option could remove those left-over members immediately.

      + When long session timeout has been configured, active members could take longer to get expired on the broker thus blocking the reset job to complete. Use the --force option could remove those left-over members immediately. Make sure to shut down all stream applications when this option is specified to avoid unexpected rebalances.

    • Use this tool with care and double-check its parameters: If you provide wrong parameter values (e.g., typos in application.id) or specify parameters inconsistently (e.g., specify the wrong input topics for the application), this tool might invalidate the application’s state or even impact other applications, consumer groups, or your Kafka topics.

      • @@ -118,7 +118,7 @@

      Step 1: Run the application reset tool