rework server bootstrap completion #800
Merged
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.
Description
margo_state_dump()
on client-server or server-server failures (currently commented out)unifyfs_invoke_broadcast_extents()
Motivation and Context
Flash-X on OLCF Summit was consistently failing to bootstrap at 12 nodes. Some of the servers were ready for client connections while others were still in the bootstrap phase.
Previously, servers assumed a successful "server bootstrap" phase when they received a response to the RPC used to report their pid to rank 0. These changes ensure that every server reaches consensus on bootstrap completion before we generate the unifyfs_server.pids file that is used by the command-line utility to report success in a user job.
How Has This Been Tested?
Tested on OLCF Summit. Getting to a working config required use of margo 0.13.1, mercury 2.2, argobots 1.1, and libfabric 1.14.1
Types of changes
Checklist: