You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
Pull Request resolved: meta-pytorch#892
`fbcode//monarch/hyperactor_mesh:hyperactor_mesh_proxy_test` is a standalone self bootstrapping program that uses `ProcessAllocator` to do the following:
- the driver creates a proc/process to host a `ProxyActor`
- initialization of the `ProxyActor` on the new proc/process creates a proc/process to host a `TestActor`
so, executing this program creates a 3 level process hierarchy `driver -> parent -> grandchild` where the `parent` process hosts a single proc/process (rank = 0) with one `ProxyActor` and the `grandchild` a single proc/process (rank = 0) with one `TestActor`.
using this program, i observe that as things stand, logs from the parent and the grandchild (since they share a common rank) are merged in the one file `/tmp/$USER/monarch_log_0.stdout`.
this diff disambiguates proc logs by incorporating the process ID of the mesh owner into the proc's log file name.
so, for example, now there will be logs `monarch_log_3529266_0.stdout` (capturing the logs of the parent proc) and `monarch_log_3530444_0.stdout` (capturing the logs of the grandchild proc).
Reviewed By: highker
Differential Revision: D80349615
fbshipit-source-id: 3c37864fa3d5fe327f1d1e679df583fd5e023475
0 commit comments