From 136f584c05c1d381544a95cfcde7adc43f6a7ae9 Mon Sep 17 00:00:00 2001 From: zhaohaidao Date: Mon, 5 Apr 2021 23:11:58 +0800 Subject: [PATCH] KAFKA-12615: Fix `Selector.clear()` javadoc typo (#10477) The second `clearCompletedSends()` reference should be `clearCompletedReceives()`. Reviewers: Ismael Juma Co-authored-by: Zhao Haiyuan --- .../src/main/java/org/apache/kafka/common/network/Selector.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/clients/src/main/java/org/apache/kafka/common/network/Selector.java b/clients/src/main/java/org/apache/kafka/common/network/Selector.java index 33f587f4809..38880f2038e 100644 --- a/clients/src/main/java/org/apache/kafka/common/network/Selector.java +++ b/clients/src/main/java/org/apache/kafka/common/network/Selector.java @@ -825,7 +825,7 @@ public class Selector implements Selectable, AutoCloseable { * Clears all the results from the previous poll. This is invoked by Selector at the start of * a poll() when all the results from the previous poll are expected to have been handled. *

- * SocketServer uses {@link #clearCompletedSends()} and {@link #clearCompletedSends()} to + * SocketServer uses {@link #clearCompletedSends()} and {@link #clearCompletedReceives()} to * clear `completedSends` and `completedReceives` as soon as they are processed to avoid * holding onto large request/response buffers from multiple connections longer than necessary. * Clients rely on Selector invoking {@link #clear()} at the start of each poll() since memory usage