1adb3a6cda
The optimization that was introduced a year ago for saving a collective synchronization step for certain communicator creation functions has to be disabled for now. The bug has been exposed by the hierarch module, but could appear as well for inter-communicator creations. The problem is, that within a communicator creation step we invoke a comm_dup (for intercomm_create) or other collective operations (in case of hierarch) before all processes have been synchronized. This lead to the "Dropped message for non-existant communicators" error. This commit disables the optimization without removing it from the code base. In theory, it can be enabled again as soon as we have the unexpected message queues for unknown cid's, which were required if I remember right anyway for the multi-threaded scenarios and potentially for fault tolerance. Before moving the patch to 1.3 I would like to let it soak for a couple of days on trunk. Please note, taht my 2nd comment on ticket #1408 was semi-correct, since the order of activation of the communicator and quering the collective module have already been changed earlier. This commit was SVN r19139. The following Trac tickets were found above: Ticket 1408 --> https://svn.open-mpi.org/trac/ompi/ticket/1408 |
||
|---|---|---|
| .. | ||
| comm_cid.c | ||
| comm_init.c | ||
| comm.c | ||
| communicator.h | ||
| Makefile.am | ||