[
https://issues.apache.org/jira/browse/KAFKA-13572?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Luke Chen resolved KAFKA-13572.
---
Fix Version/s: 3.3.0
3.2.1
Resolution: Fixed
> Negative value for 'Preferr
rui created KAFKA-14080:
---
Summary: too many node disconnected message in kafka-clients
Key: KAFKA-14080
URL: https://issues.apache.org/jira/browse/KAFKA-14080
Project: Kafka
Issue Type: Bug
C
I submitted a tweaked PR for 3.3.0 based on the 3.2.1 fix here:
https://github.com/apache/kafka/pull/12415
On Sun, Jul 17, 2022 at 1:52 PM Chris Egerton
wrote:
> Hi all,
>
> Although KAFKA-14079 is not a regression, it'd be nice if we could get it
> into 3.3.0. As I mentioned on the 3.2.1 releas
Hi Chris E.
Thanks for all the feedback earlier, I updated the PR based on your
comments and also pushed a second PR for trunk for 3.3.0
I agree the impact is high which is why I found the issue. I recently
turned on this feature and suddenly my connect worker/task kept
periodically falling over
Hi all,
Although KAFKA-14079 is not a regression, it'd be nice if we could get it
into 3.3.0. As I mentioned on the 3.2.1 release thread, the risk is fairly
low (the functional changes are just two lines long), and the impact is
high for users who have configured source connectors with
"errors.tol
Hi Chris,
Good find, and thanks for filing a fix. I agree that we should get this
into 3.2.1 if possible. The risk is fairly low (the functional parts of the
fix are just two lines long) and the impact of the bug is high for users
who have configured source connectors with "errors.tolerance" set t
