Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenSSL 3 error 0A000126 can cause an offset reset #4293

Closed
6 of 7 tasks
emasab opened this issue May 25, 2023 · 1 comment
Closed
6 of 7 tasks

OpenSSL 3 error 0A000126 can cause an offset reset #4293

emasab opened this issue May 25, 2023 · 1 comment

Comments

@emasab
Copy link
Contributor

emasab commented May 25, 2023

Description

An unclean SSL close, possibly caused by a TCP reset, causes a RD_KAFKA_RESP_ERR__SSL error. If it happens during offset validation it can cause an offset reset because it's treated as permanent.

How to reproduce

cause an unexpected EOF during a OffsetForLeaderEpoch call.

Checklist

Please provide the following information:

  • librdkafka version 2.1.0, 2.1.1
  • Apache Kafka version: 3.4.0
  • librdkafka client configuration: unimportant
  • Operating system: unimportant
  • Provide logs (with debug=.. as necessary) from librdkafka
  • Provide broker log excerpts
  • Critical issue
 %3|1683846206.615|FAIL|... REDACTED...: SSL handshake failed: error:0A000126:SSL routines::unexpected eof while reading (after 5002ms in state SSL_HANDSHAKE)
%4|1683846206.616|OFFSET|... REDACTED...: offset reset (at offset INVALID (leader epoch 41), broker 25) to offset BEGINNING (leader epoch -1): Unable to validate offset and epoch: Local: SSL error: Local: Partition log truncation detected
emasab added a commit that referenced this issue May 26, 2023
and treat unclean SSL  closes as normal ones

fixes #4293
emasab added a commit that referenced this issue May 26, 2023
and treat unclean SSL  closes as normal ones

fixes #4293
@emasab emasab closed this as completed in 3e39a9e Jun 14, 2023
@RefaelP23
Copy link

@emasab Is there an estimate on when this fix will be released?
We noticed this issue with the .Net client as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants