48fc339718
onto the backend daemons. By default, let mpirun only pack the app_context info and send that to the backend daemons where the mapping will be done. This significantly reduces the computational time on mpirun as it isn't running up/down the topology tree computing thousands of binding locations, and it reduces the launch message to a very small number of bytes. When running -novm, fall back to the old way of doing things where mpirun computes the entire map and binding, and then sends the full info to the backend daemon. Add a new cmd line option/mca param --fwd-mpirun-port that allows mpirun to dynamically select a port, but then passes that back to all the other daemons so they will use that port as a static port for their own wireup. In this mode, we no longer "phone home" directly to mpirun, but instead use the static port to wireup at daemon start. We then use the routing tree to rollup the initial launch report, and limit the number of open sockets on mpirun's node. Update ras simulator to track the new nidmap code Cleanup some bugs in the nidmap regex code, and enhance the error message for not enough slots to include the host on which the problem is found. Update gadget platform file Initialize the range count when starting a new range Fix the no-np case in managed allocation Ensure DVM node usage gets cleaned up after each job Update scaling.pl script to use --fwd-mpirun-port. Pre-connect the daemon to its parent during launch while we are otherwise waiting for the daemon's children to send their "phone home" rollup messages Signed-off-by: Ralph Castain <rhc@open-mpi.org>
65 строки
2.6 KiB
Plaintext
65 строки
2.6 KiB
Plaintext
# -*- text -*-
|
|
#
|
|
# Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
|
|
# University Research and Technology
|
|
# Corporation. All rights reserved.
|
|
# Copyright (c) 2004-2005 The University of Tennessee and The University
|
|
# of Tennessee Research Foundation. All rights
|
|
# reserved.
|
|
# Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
# University of Stuttgart. All rights reserved.
|
|
# Copyright (c) 2004-2005 The Regents of the University of California.
|
|
# All rights reserved.
|
|
# Copyright (c) 2017 Intel, Inc. All rights reserved.
|
|
# $COPYRIGHT$
|
|
#
|
|
# Additional copyrights may follow
|
|
#
|
|
# $HEADER$
|
|
#
|
|
# This is the US/English general help file for Open RTE's orterun.
|
|
#
|
|
[orte-rmaps-rr:alloc-error]
|
|
There are not enough slots available in the system to satisfy the %d slots
|
|
that were requested:
|
|
|
|
application: %s
|
|
host: %s
|
|
|
|
Either request fewer slots for your application, or make more slots available
|
|
for use.
|
|
[orte-rmaps-rr:multi-apps-and-zero-np]
|
|
RMAPS found multiple applications to be launched, with
|
|
at least one that failed to specify the number of processes to execute.
|
|
When specifying multiple applications, you must specify how many processes
|
|
of each to launch via the -np argument.
|
|
|
|
[orte-rmaps-rr:per-node-and-too-many-procs]
|
|
There are not enough nodes in your allocation to satisfy your request to launch
|
|
%d processes on a per-node basis - only %d nodes were available.
|
|
|
|
Either request fewer processes, or obtain a larger allocation.
|
|
[orte-rmaps-rr:n-per-node-and-too-many-procs]
|
|
There are not enough nodes in your allocation to satisfy your request to launch
|
|
%d processes on a %d per-node basis - only %d nodes with a total of %d slots were available.
|
|
|
|
Either request fewer processes, or obtain a larger allocation.
|
|
[orte-rmaps-rr:n-per-node-and-not-enough-slots]
|
|
There are not enough slots on the nodes in your allocation to satisfy your request to launch on a %d process-per-node basis - only %d slots/node were available.
|
|
|
|
Either request fewer processes/node, or obtain a larger allocation.
|
|
|
|
[orte-rmaps-rr:no-np-and-user-map]
|
|
You have specified a rank-to-node/slot mapping, but failed to provide
|
|
the number of processes to be executed. For some reason, this information
|
|
could not be obtained from the mapping you provided, so we cannot continue
|
|
with executing the specified application.
|
|
#
|
|
[orte-rmaps-rr:not-enough-objs]
|
|
There are not enough resources on the available nodes
|
|
to meet the requested mapping.
|
|
|
|
Application: %s
|
|
Number of procs: %d
|
|
Number of resources: %d
|