[
https://issues.apache.org/jira/browse/KAFKA-9854?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261205#comment-17261205
]
Alexandru Ionescu commented on KAFKA-9854:
------------------------------------------
Hello,
I was not able to reproduce this. We have an OpenShift cluster with 3 instance
Kafka installed using Strimzi Operator and OAUTHBEARER / SASL_PLAINTEXT
security. This issue happens randomly for each consumer once every few hours /
days.
What is strange is that if I have 2 instance of the same application that
consumes, the consumer group appears STABLE after this error, but the consumer
no longer reads certain partitions.
Any ideas on how to reproduce this or how to investigate further?
Best regards,
Alex
> Re-authenticating causes mismatched parse of response
> -----------------------------------------------------
>
> Key: KAFKA-9854
> URL: https://issues.apache.org/jira/browse/KAFKA-9854
> Project: Kafka
> Issue Type: Bug
> Reporter: Chia-Ping Tsai
> Assignee: Chia-Ping Tsai
> Priority: Critical
> Fix For: 2.6.0, 2.5.1
>
>
> the schema of LIST_OFFSETS consists of
> # throttle_time_ms:INT32 and
> # responses:ARRAY
>
> If throttle_time_ms is zero and size of responses is small enough, its
> binary is compatible to schema of SASL_HANDSHAKE composed of
> # error_code:INT16 and
> # mechanisms:ARRAY(STRING)
>
> Hence, there is no Schema error when SASL_HANDSHAKE tries to parse response
> of LIST_OFFSETS but the check of correction id throws IllegalStateException
> due to mismatched error. The IllegalStateException is NOT caught and the
> mismatched response is not sent back to Selector so the cascading error
> happens that all following responses are parsed by incorrect Schema.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
