pingcap / pingcap/tiproxy

TiProxy keeps reporting errors for HAProxy health check

Open
#478 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
73
Forks
41
Avg merge
21h 3m
Merged PRs (30d)
21

Description

Bug Report

Please answer these questions before submitting your issue. Thanks!

1. Minimal reproduce step (Required)
  1. Start HAProxy and set the health check port to 6000 of TiProxy
  2. Start TiProxy
2. What did you expect to see? (Required)

No errors in TiProxy

3. What did you see instead (Required)

TiProxy keeps reporting:

[2024/02/28 15:43:14.752 +08:00] [WARN] [main.proxy] [proxy/proxy.go:206] [failed to set tcp keep alive option] [connID=15] [client_addr=127.0.0.1:62842] [addr=0.0.0.0:6000] [error="failed to set keepalive and timeout: set tcp [::7f00:1]:6000->127.0.0.1:62842: setsockopt: invalid argument"]
[2024/02/28 15:43:15.157 +08:00] [WARN] [main.proxy] [proxy/proxy.go:206] [failed to set tcp keep alive option] [connID=16] [client_addr=127.0.0.1:62845] [addr=0.0.0.0:6000] [error="failed to set keepalive and timeout: set tcp 127.0.0.1:6000->127.0.0.1:62845: setsockopt: invalid argument"]
[2024/02/28 15:43:20.757 +08:00] [WARN] [main.proxy] [proxy/proxy.go:206] [failed to set tcp keep alive option] [connID=17] [client_addr=127.0.0.1:62855] [addr=0.0.0.0:6000] [error="failed to set keepalive and timeout: set tcp 127.0.0.1:6000->127.0.0.1:62855: setsockopt: invalid argument"]
[2024/02/28 15:43:23.164 +08:00] [WARN] [main.proxy] [proxy/proxy.go:206] [failed to set tcp keep alive option] [connID=18] [client_addr=127.0.0.1:62862] [addr=0.0.0.0:6000] [error="failed to set keepalive and timeout: set tcp [::7f00:1]:6000->127.0.0.1:62862: setsockopt: invalid argument"]
4. What is your version? (Required)

master

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue by starting HAProxy with TiProxy's health-check port set to 6000, then inspect proxy/proxy.go around line 206 and the reported TCP keepalive warning. Determine why the health check produces an invalid-argument error; done means the health check no longer causes these warnings without breaking the connection handling.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
networking
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.