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

server: proxy protocol fallback feature will return header read timeout error when underlay connection read got error #43205

Closed
blacktear23 opened this issue Apr 19, 2023 · 0 comments · Fixed by #43189

Comments

@blacktear23
Copy link
Contributor

Bug Report

Please answer these questions before submitting your issue. Thanks!

server: proxy protocol fallback feature will return header read timeout error when underlay connection read got error

1. Minimal reproduce step (Required)

start tidb with fallbackable=true
echo -ne "" | nc  localhost 4000 &> /dev/null
[2023/04/18 17:02:37.376 +08:00] [WARN] [server.go:612] ["Server.onConn handshake"] [conn=2199023255981] [error="Header read timeout"] ["remote addr"="[::1]:60100"]

2. What did you expect to see? (Required)

the error that conn.Read actually returned.

3. What did you see instead (Required)

got Header read timeout error.

4. What is your TiDB version? (Required)

master

@blacktear23 blacktear23 added the type/bug This issue is a bug. label Apr 19, 2023
@ti-chi-bot ti-chi-bot added may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. may-affects-6.1 may-affects-6.5 may-affects-7.1 labels Apr 20, 2023
@hawkingrei hawkingrei removed may-affects-5.1 This bug maybe affects 5.1.x versions. may-affects-5.2 This bug maybe affects 5.2.x versions. may-affects-5.3 This bug maybe affects 5.3.x versions. may-affects-5.4 This bug maybe affects 5.4.x versions. labels Apr 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants