On Sat, Apr 7, 2018 at 3:50 PM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> wrote: > On Apr 6, 2018, at 8:12 AM, Michael Di Domenico <mdidomeni...@gmail.com> > wrote: >> it would be nice if openmpi had (or may already have) a simple switch >> that lets me disable entire portions of the library chain, ie this >> host doesn't have a particular interconnect, so don't load any of the >> libraries. this might run counter to how openmpi discovers and load >> libs though. > > We've actually been arguing about exactly how to do this for quite a while. > It's complicated (I can explain further, if you care). :-\
i have no doubt its complicated. i'm not overly interested in the detail, but others i'm sure might be. in reality you're correct, i don't care that openmpi failed to load the libs given the fact that the job continues to run without issue. and in fact i don't even care about the warnings, but my users will complain and ask questions. achieving a single build binary where i can disable the interconnects/libraries at runtime would be HIGHLY beneficial to me (perhaps others as well). it cuts my build version combinations from like 12 to 4 (or less), that's a huge reduction in labour/maintenance. which also means i can upgrade openmpi quicker and stay more up to date. i would garner this is probably not a high priority for the team working on openmpi, but if there's something my organization or I can do to push this higher, let me know. > That being said, I think we *do* have a workaround that might be good enough > for you: disable those warnings about plugins not being able to be opened: > mpirun --mca mca_component_show_load_errors 0 ... disabled this: mca_base_component_repository_open: unable to open mca_oob_ud: libibverbs.so.1 but not this: pmix_mca_base_component_repository_open: unable to open mca_pnet_opa: libpsm2.so.2 _______________________________________________ users mailing list users@lists.open-mpi.org https://lists.open-mpi.org/mailman/listinfo/users
