abbccdda commented on a change in pull request #8760:
URL: https://github.com/apache/kafka/pull/8760#discussion_r432900674
##########
File path: docs/streams/developer-guide/app-reset-tool.html
##########
@@ -117,6 +118,9 @@ <h2>Step 1: Run the application reset tool<a
class="headerlink" href="#step-1-ru
bootstrap.servers, as the reset tool
would no longer access Zookeeper
directly.
+--force Force the removal of members of the
consumer group
Review comment:
nit: `Force the removal of` -> `Force removing`
##########
File path: docs/streams/developer-guide/app-reset-tool.html
##########
@@ -56,7 +56,8 @@
<dl class="docutils">
<dt>Prerequisites</dt>
<dd><ul class="first last">
- <li><p class="first">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
<code class="docutils literal"><span class="pre">application.id</span></code>
is still active by using <code class="docutils literal"><span
class="pre">bin/kafka-consumer-groups</span></code>.</p>
+ <li><p class="first">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
<code class="docutils literal"><span class="pre">application.id</span></code>
is still active by using <code class="docutils literal"><span
class="pre">bin/kafka-consumer-groups</span></code>.
+ 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 <code class="docutils literal"><span
class="pre">--force</span></code> option could remove those left-over members
immediately.</p>
Review comment:
We should also mention the caution to look out for doing a reset on a
running application.
----------------------------------------------------------------
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:
[email protected]
