Console output got relipated n times if there are n ray nodes on the same machine
See original GitHub issueWhat is the problem?
Ray version: 0.8.7 Python version: 3.6.7
Problem:
If multiple ray nodes (say n ray nodes) are started on the same machine, then one ray nodes’ console output will got replicated n times on driver.
Reproduction (REQUIRED)
Please provide a script that can be run to reproduce the issue. The script should have no external library dependencies (i.e., use fake or mock data / environments):
Step 1: start two ray nodes on the same machine
ray start --head
ray start --address='the address printed' --redis-password='the password printed'
Step 2: run the following script
import ray
def print_hello():
print("hello")
return 0
remote_print = ray.remote(print_hello)
ray.get(remote_print.remote())
Then “hello” will be printed twice on the driver.
If we cannot run your script, we cannot fix your issue.
- I have verified my script runs in a clean environment and reproduces the issue.
- I have verified the issue also occurs with the latest wheels.
Issue Analytics
- State:
- Created 3 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
[Core] Ray fails to log or print messages to console after ...
After a worker errors out and I attempt to run the job again, print messages or logs fail to appear in the terminal....
Read more >In Jenkins Pipelines, how can the console output from multiple ...
Is it possible to filter it so that only the console output of a single node is shown without having to dig through...
Read more >What I miss with Pipeline: Console output from each node
I have been using Jenkins Multi-configuration. With my move over to Pipeline scripts and Jenkinsfile I still build on multiple nodes/slaves.
Read more >Using Ray on a Cluster — Ray 0.01 documentation
This section assumes that you have a cluster running and that the nodes in the cluster can ... It also assumes that Ray...
Read more >1.13.2 - No Console Output? - Modder Support - Forge Forums
I just set up Forge for 1.13.2, and in an effort to ensure I set ... but when I enter my minecraft crashes...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@rkooo567 https://github.com/ray-project/ray/blob/master/python/ray/node.py#L233, seems non-head ray process just read the “temp_dir” set to head node, and each ray node cannot be assigned to different log dir.
I worked around this issue by manually killing the redundant log_monitor processes. However, I think it would be nice to support it in ray. E.g. separating each ray nodes’ log dir to “/tmp/ray/session-xx/0/logs”, “/tmp/ray/session-xxx/1/logs”, .etc
I’ll close this issue for now since you will open a new issue with the repro