You can use MPI_Abort(MPI_COMM_SELF,0) to exit a process locally.
This may abort world if errors are fatal but either way, it’s not going to
synchronize before processes go poof.
Jeff
On Fri 9. Sep 2022 at 21.34 Mccall, Kurt E. (MSFC-EV41) via users <
users@lists.open-mpi.org> wrote:
> Hi,
>
>
mpirun reports the following error:The OSC pt2pt component does not support MPI_THREAD_MULTIPLE in this release.Workarounds are to run on a single node, or to use a system with an RDMAcapable network such as Infiniband.Does this error mean that the network must support RDMA if it
Hi all,
I have the following use case. I have N mpi ranks in the global
communicator, and I split it into two, first being rank 0, and the other
being all ranks from 1-->N-1.
Rank0 acts as a master and ranks [1, N-1] act as workers. I use rank0 to
broadcast (blocking) a set of values to ranks [1,
No, it does not, sorry.
What are you trying to do?
--
Jeff Squyres
jsquy...@cisco.com
From: users on behalf of Mccall, Kurt E.
(MSFC-EV41) via users
Sent: Friday, September 9, 2022 2:30 PM
To: OpenMpi User List (users@lists.open-mpi.org)
Cc: Mccall, Kurt E. (M
Hi,
If a single process needs to exit, MPI_Finalize will pause at a barrier,
possibly waiting for pending communications to complete. Does OpenMPI have any
means to disable this behavior, so the a single process can exit normally if
the application calls for it?
Thanks,
Kurt
