client: logspam while not able to connect to a server
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
In playing with a disconnected client I notice Client logs are spamming these messages multiple times per second. We should refrain from log spam and log at most like once per second, if that.
2023-04-28T19:07:52.065Z [WARN] client.server_mgr: no servers available
2023-04-28T19:07:52.204Z [WARN] client.server_mgr: no servers available
2023-04-28T19:07:52.205Z [WARN] client.server_mgr: no servers available
2023-04-28T19:07:52.354Z [WARN] client.server_mgr: no servers available
2023-04-28T19:07:52.368Z [WARN] client.server_mgr: no servers available
2023-04-28T19:07:52.620Z [WARN] client.server_mgr: no servers available
2023-04-28T19:07:52.902Z [WARN] client.server_mgr: no servers available
2023-04-28T19:07:52.949Z [WARN] client.server_mgr: no servers available
2023-04-28T19:07:53.183Z [WARN] client.server_mgr: no servers available
Contributor guide
No contributing guide indexed for this repository
Research direction
Start at the client.server_mgr path that emits the “no servers available” warning and reproduce the disconnected-client behavior. The issue is done when repeated connection failures no longer produce more than about one warning per second.
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
- Mostly clear
- Newbie friendliness
- 45/100