Repository navigation
docs: clients of earlier PMIx releases need legacy peers - #2879
Merged
Merged
Conversation
With PMIx v7.0 or later, a daemon's PMIx server takes clients and tools of earlier PMIx releases - an Open MPI 5 application, or a prun built against an earlier PMIx - only with legacy peers on. Without them each such process comes up as a singleton, so an N-process job runs as N one-process jobs, with one PMIX ERROR: BAD-PARAM line apiece. Say so in the troubleshooting guide, by the symptom, with the remedy: a PMIx built with --enable-legacy-peers, and ptl_base_legacy_peers set through --pmixmca or PMIX_MCA_ptl_base_legacy_peers, which reach every daemon of the DVM. Signed-off-by: Ralph Castain <rhc@pmix.org>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Docs only.
With PMIx v7.0 or later, a daemon's PMIx server accepts clients and tools of earlier PMIx releases only when legacy peers are on. That covers, for example, an Open MPI 5 application or a
prunbuilt against an earlier PMIx. Without legacy peers, each such process comes up as a singleton, so an N-process job runs as N one-process jobs, each logging onePMIX ERROR: BAD-PARAMline.The troubleshooting guide now has an entry for that symptom, with the remedy:
--enable-legacy-peers;ptl_base_legacy_peerswith--pmixmca, or withPMIX_MCA_ptl_base_legacy_peersin the environment.Either setting reaches every daemon: schizo exposes
--pmixmcavalues asPMIX_MCA_*variables, and the daemon launch forwards those.Testing
sphinx-buildadds no warnings.prterun --report-uri tcp-prints a TCP URI with either one, and is refused without).