Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[WIP] use TCPSocket to determine worker ip and port #46996

Closed
wants to merge 3 commits into from
Closed

[WIP] use TCPSocket to determine worker ip and port #46996

wants to merge 3 commits into from

Conversation

Moelf
Copy link
Contributor

@Moelf Moelf commented Oct 1, 2022

@Moelf
Copy link
Contributor Author

Moelf commented Oct 1, 2022

while this makes the addproc no long hang, I still run into:

 caused by: IOError: connect: connection refused (ECONNREFUSED)
    Stacktrace:
     [1] wait_connected(x::Sockets.TCPSocket)
       @ Sockets ~/julia-1.8.1/share/julia/stdlib/v1.8/Sockets/src/Sockets.jl:529
     [2] connect
       @ ~/julia-1.8.1/share/julia/stdlib/v1.8/Sockets/src/Sockets.jl:564 [inlined]
     [3] connect_to_worker(host::String, port::Int64)
       @ Distributed ~/julia-1.8.1/share/julia/stdlib/v1.8/Distributed/src/managers.jl:651
     [4] connect(manager::HTCManager, pid::Int64, config::WorkerConfig)
       @ Distributed ~/julia-1.8.1/share/julia/stdlib/v1.8/Distributed/src/managers.jl:578

I'm wondering if this is because the worker node is not listening correctly (same reason why it printed the wrong IP address in the first place)

@Moelf Moelf changed the title use TCPSocket to determine worker ip and port [WIP] use TCPSocket to determine worker ip and port Oct 1, 2022
@Moelf Moelf closed this Oct 2, 2022
@Moelf Moelf deleted the use_worker_tcpsocket_for_binaddr branch October 2, 2022 05:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Distributed worker manager doesn't use socket connection to infer worker ip
1 participant
@Moelf