[C++][Flight] Improve error message when port cannot be bound with gRPC
Open
Component: FlightRPC
Type: enhancement
- Dominant language
- C++
- Stars
- 17.1k
- Forks
- 4.3k
- Avg merge
- 3d 13h
- Merged PRs (30d)
- 88
Description
### Describe the enhancement requested
Currently, when starting a flight server fails because the call to `arrow::flight::FlightServerBase::Init()` fails internally at the gRPC `BuildAndStart()` step, the error message is rather vague about the reason.
A pretty common error while starting the server is that the supplied port cannot be used; this is indicated by `selected_port` that is populated after `BuildAndStart()`, so the error message could be improved here.
### Component(s)
FlightRPC
Contributor guide
Assessment
This issue has not been assessed yet.