Sorry for late response. But I just wanted to inform you that I found
another workaround, unrelated to the method we discussed here.
On 19/06/18 15:26, r...@open-mpi.org wrote:
The OMPI cmd line converts "--mca ptl_tcp_remote_connections 1” to OMPI_MCA_
ptl_tcp_remote_connections, which is not recognized by PMIx. PMIx is looking for
PMIX_MCA_ptl_tcp_remote_connections. The only way to set PMIx MCA params for the
code embedded in OMPI is to put them in your environment
On Jun 19, 2018, at 2:08 AM, Maksym Planeta <mplan...@os.inf.tu-dresden.de>
wrote:
But what about remote connections parameter? Why is it not set?
On 19/06/18 00:58, r...@open-mpi.org wrote:
I’m not entirely sure I understand what you are trying to do. The
PMIX_SERVER_URI2 envar tells local clients how to connect to their local PMIx
server (i.e., the OMPI daemon on that node). This is always done over the
loopback device since it is a purely local connection that is never used for
MPI messages.
I’m sure that the tcp/btl is using your indicated subnet as that would be used
for internode messages.
--
Regards,
Maksym Planeta
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
--
Regards,
Maksym Planeta
_______________________________________________
users mailing list
users@lists.open-mpi.org
https://lists.open-mpi.org/mailman/listinfo/users
