I'm using OpenMPI 2.1.0 on RHEL 7, communicating between ranks via TCP
I have a new cluster to install my application on with tightly-controlled
firewalls. I can have them open up a range of TCP ports which MPI can
communicate over. I thought I could force MPI to stick to a range of ports
via "-
I suspect the OOB is working just fine and you are seeing the TCP/btl opening
the other ports. There are two TCP elements at work here: the OOB (which sends
management messages between daemons) and the BTL (which handles the MPI
traffic). In addition to what you provided, you also need to provid
Aha - thanks Ralph! I'll give that a shot.
-Adam
On Sat, Jul 7, 2018 at 10:36 AM, r...@open-mpi.org wrote:
> I suspect the OOB is working just fine and you are seeing the TCP/btl
> opening the other ports. There are two TCP elements at work here: the OOB
> (which sends management messages betw
Hi,
It appears that MPI_Comm_get_attr fails to get MPI_TAG_UB for
sub-communicators created by MPI_Comm_split. I have tested the following
programs with openmpi 3.1.1 and openmpi 1.10.2. MPI_Comm_get_attr works on
MPI_COMM_WORLD, but not on sub-communicators. Is this expected?
#include
#inclu
