You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we use version 2.6.0, the api version negotation fails to correctly set the fetch request's version to something the server supports. We use an internal Redis-backed implementation of Kafka for testing in Docker containers that only supports up to v7 of the Fetch request. However, the newest client fails to select the correct version and instead sends v12 for fetch requests.
The same problem occurred on our production Kafka cluster running Kafka version 2.6.1 with a TLS connection. All other interactions between the consumer and the cluster seemed to work correctly.
The problem does not occur when we use version 2.5.3.
The text was updated successfully, but these errors were encountered:
misalcedo
changed the title
Bug with v2.6.0 during version negotiation for fetch requests.
Bug with v2.6.0 during version negotiation.
Oct 21, 2024
When we use version 2.6.0, the api version negotation fails to correctly set the fetch request's version to something the server supports. We use an internal Redis-backed implementation of Kafka for testing in Docker containers that only supports up to v7 of the Fetch request. However, the newest client fails to select the correct version and instead sends v12 for fetch requests.
The same problem occurred on our production Kafka cluster running Kafka version 2.6.1 with a TLS connection. All other interactions between the consumer and the cluster seemed to work correctly.
The problem does not occur when we use version 2.5.3.
The text was updated successfully, but these errors were encountered: