find a proper way to handle fail during proxy initializing
Open
Nobody has claimed this yet.
type/enhancement
- Dominant language
- C++
- Stars
- 1k
- Forks
- 423
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 24
Description
Enhancement
Now TiFlash server will keep on waiting for proxy init by checking whether proxy_helper is nullptr. But the proxy may fail before setting proxy. TiFlash can not be aware that proxy has failed, just keep on waiting...
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at dbms/src/Server/Server.cpp around lines 1040-1043 and trace how proxy initialization reports success or failure. Determine how the server can distinguish a failed initialization from an unset proxy, then verify that it no longer waits indefinitely when proxy initialization fails.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100