JuliaLang / JuliaLang/Distributed.jl
Distributed worker manager doesn't use socket connection to infer worker ip
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 55
- Forks
- 19
- PR merge metrics
- No merged PRs in 30d
Description
for some reason we don't use the fact that we can call Sockets.getpeername() here, instead we read the stdout of the worker process.
This is problemmatic mainly because:
-
the worker nodes always report the first IPv4 interface's address no matter if that's actually the interface it used to contact main node:
https://github.com/JuliaLang/julia/blob/0d00660a38f4d4049e12a97399e4ef613bf0d7dc/stdlib/Sockets/src/addrinfo.jl#L272-L276 -
the worker node may be running inside container (or whatever reason has virtual interface before everything else)
my questions: can we add a specialization for read_worker_host_port when config.io :: Sockets.TCPSocket?
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 in stdlib/Distributed/src/managers.jl at read_worker_host_port and inspect the Sockets.TCPSocket handling, then compare how Sockets/src/addrinfo.jl determines addresses. Done means TCP workers use the socket peer address rather than stdout-derived or first-interface data, including when the worker runs behind a virtual or container interface.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- julia
- Domain
- distributed-systems, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100