Why would anyone use connect/accept (or join) between processes on the same job? The only environment where such a functionality makes sense is where disjoint applications (think computing part and the visualization part) are able to connect together. There are application that use such a model, but I bet they don't use OMPI.
George. On Tue, Sep 8, 2015 at 4:50 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > On Sep 7, 2015, at 5:07 PM, Ralph Castain <r...@open-mpi.org> wrote: > > > > * two jobs started by the same mpirun - supported today by ORTE > > > > * two jobs started by different mpiruns - we used to support, but is > broken in grpcomm/barrier > > > > * two direct-launched jobs - never supported > > > > * one direct-launched job and one started by mpirun - never supported > > > > Given lack of use out there, I don’t see a reason to hold release of the > 2.x series over this issue. Will keep you posted on progress towards a > resolution > > +1 > > That being said, I think it *would* be useful to be able to connect/accept > between "two jobs started by different mpiruns." It's a bit of a > chicken-n-egg problem: no one does it because no one supports it, and vice > versa. > > I agree it's low in the priority list, but I'd put the "two jobs started > by different mpiruns" in the "nice to have" category. > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > devel mailing list > de...@open-mpi.org > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/devel > Link to this post: > http://www.open-mpi.org/community/lists/devel/2015/09/17983.php
