2005-03-14 23:57:21 +03:00
|
|
|
/*
|
2005-11-05 22:57:48 +03:00
|
|
|
* Copyright (c) 2004-2005 The Trustees of Indiana University and Indiana
|
|
|
|
* University Research and Technology
|
|
|
|
* Corporation. All rights reserved.
|
2006-08-23 07:32:36 +04:00
|
|
|
* Copyright (c) 2004-2006 The University of Tennessee and The University
|
2005-11-05 22:57:48 +03:00
|
|
|
* of Tennessee Research Foundation. All rights
|
|
|
|
* reserved.
|
2005-03-14 23:57:21 +03:00
|
|
|
* Copyright (c) 2004-2005 High Performance Computing Center Stuttgart,
|
|
|
|
* University of Stuttgart. All rights reserved.
|
2005-03-24 15:43:37 +03:00
|
|
|
* Copyright (c) 2004-2005 The Regents of the University of California.
|
|
|
|
* All rights reserved.
|
2006-05-16 18:14:12 +04:00
|
|
|
* Copyright (c) 2006 Cisco Systems, Inc. All rights reserved.
|
2007-06-05 07:03:59 +04:00
|
|
|
* Copyright (c) 2007 Los Alamos National Security, LLC. All rights
|
|
|
|
* reserved.
|
2005-03-14 23:57:21 +03:00
|
|
|
* $COPYRIGHT$
|
|
|
|
*
|
|
|
|
* Additional copyrights may follow
|
|
|
|
*
|
|
|
|
* $HEADER$
|
|
|
|
*
|
|
|
|
* These symbols are in a file by themselves to provide nice linker
|
|
|
|
* semantics. Since linkers generally pull in symbols by object
|
|
|
|
* files, keeping these symbols as the only symbols in this file
|
|
|
|
* prevents utility programs such as "ompi_info" from having to import
|
|
|
|
* entire components just to query their version and parameters.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#include "orte_config.h"
|
2008-02-28 04:57:57 +03:00
|
|
|
#include "orte/constants.h"
|
|
|
|
#include "orte/types.h"
|
2005-03-14 23:57:21 +03:00
|
|
|
|
|
|
|
#if HAVE_UNISTD_H
|
|
|
|
#include <unistd.h>
|
|
|
|
#endif
|
|
|
|
#include <signal.h>
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
#ifdef HAVE_SYS_TYPES_H
|
2005-03-18 06:43:59 +03:00
|
|
|
#include <sys/types.h>
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
#endif
|
2007-08-14 22:44:52 +04:00
|
|
|
#ifdef HAVE_SYS_STAT_H
|
|
|
|
#include <sys/stat.h>
|
|
|
|
#endif
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
#ifdef HAVE_SYS_WAIT_H
|
2005-03-18 06:43:59 +03:00
|
|
|
#include <sys/wait.h>
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
#endif
|
2005-08-19 20:49:59 +04:00
|
|
|
#ifdef HAVE_SCHED_H
|
|
|
|
#include <sched.h>
|
|
|
|
#endif
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
#ifdef HAVE_SYS_TIME_H
|
|
|
|
#include <sys/time.h>
|
|
|
|
#endif
|
2005-08-19 20:49:59 +04:00
|
|
|
#include <errno.h>
|
|
|
|
#include <tm.h>
|
2005-03-14 23:57:21 +03:00
|
|
|
|
2007-04-21 04:15:05 +04:00
|
|
|
#include "opal/mca/installdirs/installdirs.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
#include "opal/threads/condition.h"
|
2006-07-05 00:12:35 +04:00
|
|
|
#include "opal/event/event.h"
|
2005-07-04 04:13:44 +04:00
|
|
|
#include "opal/util/argv.h"
|
2008-06-09 18:53:58 +04:00
|
|
|
#include "orte/util/show_help.h"
|
2005-07-04 05:36:20 +04:00
|
|
|
#include "opal/util/opal_environ.h"
|
2005-10-04 23:38:51 +04:00
|
|
|
#include "opal/util/path.h"
|
2006-05-16 18:14:12 +04:00
|
|
|
#include "opal/util/basename.h"
|
2005-08-25 02:20:51 +04:00
|
|
|
#include "opal/mca/base/mca_base_param.h"
|
2005-08-19 20:49:59 +04:00
|
|
|
#include "opal/runtime/opal_progress.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
#include "orte/util/name_fns.h"
|
|
|
|
#include "orte/runtime/orte_globals.h"
|
2005-08-25 02:20:51 +04:00
|
|
|
#include "orte/runtime/orte_wait.h"
|
|
|
|
#include "orte/mca/errmgr/errmgr.h"
|
2006-10-07 19:45:24 +04:00
|
|
|
#include "orte/mca/rmaps/rmaps.h"
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
#include "orte/mca/plm/plm.h"
|
|
|
|
#include "orte/mca/plm/base/plm_private.h"
|
|
|
|
#include "plm_tm.h"
|
2005-03-14 23:57:21 +03:00
|
|
|
|
|
|
|
|
2006-07-05 00:12:35 +04:00
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
/*
|
|
|
|
* Local functions
|
|
|
|
*/
|
2008-02-28 04:57:57 +03:00
|
|
|
static int plm_tm_init(void);
|
|
|
|
static int plm_tm_launch_job(orte_job_t *jdata);
|
|
|
|
static int plm_tm_terminate_job(orte_jobid_t jobid);
|
|
|
|
static int plm_tm_terminate_orteds(void);
|
|
|
|
static int plm_tm_signal_job(orte_jobid_t jobid, int32_t signal);
|
|
|
|
static int plm_tm_finalize(void);
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
static int plm_tm_connect(void);
|
2008-12-09 03:32:04 +03:00
|
|
|
static int plm_tm_disconnect(void);
|
2008-06-03 01:46:34 +04:00
|
|
|
static void failed_start(int fd, short event, void *arg);
|
|
|
|
|
|
|
|
/*
|
|
|
|
* Local "global" variables
|
|
|
|
*/
|
|
|
|
static opal_event_t *ev=NULL;
|
2006-09-15 01:29:51 +04:00
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
/*
|
|
|
|
* Global variable
|
|
|
|
*/
|
2008-02-28 04:57:57 +03:00
|
|
|
orte_plm_base_module_t orte_plm_tm_module = {
|
|
|
|
plm_tm_init,
|
|
|
|
orte_plm_base_set_hnp_name,
|
|
|
|
plm_tm_launch_job,
|
2008-04-14 23:36:13 +04:00
|
|
|
NULL,
|
2008-02-28 04:57:57 +03:00
|
|
|
plm_tm_terminate_job,
|
|
|
|
plm_tm_terminate_orteds,
|
|
|
|
plm_tm_signal_job,
|
|
|
|
plm_tm_finalize
|
2005-03-14 23:57:21 +03:00
|
|
|
};
|
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
/**
|
|
|
|
* Init the module
|
|
|
|
*/
|
|
|
|
static int plm_tm_init(void)
|
|
|
|
{
|
|
|
|
int rc;
|
|
|
|
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_plm_base_comm_start())) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2007-04-25 00:53:54 +04:00
|
|
|
/* When working in this function, ALWAYS jump to "cleanup" if
|
|
|
|
* you encounter an error so that orterun will be woken up and
|
|
|
|
* the job can cleanly terminate
|
|
|
|
*/
|
2008-02-28 04:57:57 +03:00
|
|
|
static int plm_tm_launch_job(orte_job_t *jdata)
|
2005-03-14 23:57:21 +03:00
|
|
|
{
|
2007-04-25 00:53:54 +04:00
|
|
|
orte_job_map_t *map = NULL;
|
2008-02-28 04:57:57 +03:00
|
|
|
orte_app_context_t **apps;
|
|
|
|
orte_node_t **nodes;
|
|
|
|
int proc_vpid_index;
|
2007-05-08 17:21:18 +04:00
|
|
|
char *param;
|
2007-04-25 00:53:54 +04:00
|
|
|
char **env = NULL;
|
2006-10-07 19:45:24 +04:00
|
|
|
char *var;
|
2007-04-25 00:53:54 +04:00
|
|
|
char **argv = NULL;
|
Per the July technical meeting:
Standardize the handling of the orte launch agent option across PLMs. This has been a consistent complaint I have received - each PLM would register its own MCA param to get input on the launch agent for remote nodes (in fact, one or two didn't, but most did). This would then get handled in various and contradictory ways.
Some PLMs would accept only a one-word input. Others accepted multi-word args such as "valgrind orted", but then some would error by putting any prefix specified on the cmd line in front of the incorrect argument.
For example, while using the rsh launcher, if you specified "valgrind orted" as your launch agent and had "--prefix foo" on you cmd line, you would attempt to execute "ssh foo/valgrind orted" - which obviously wouldn't work.
This was all -very- confusing to users, who had to know which PLM was being used so they could even set the right mca param in the first place! And since we don't warn about non-recognized or non-used mca params, half of the time they would wind up not doing what they thought they were telling us to do.
To solve this problem, we did the following:
1. removed all mca params from the individual plms for the launch agent
2. added a new mca param "orte_launch_agent" for this purpose. To further simplify for users, this comes with a new cmd line option "--launch-agent" that can take a multi-word string argument. The value of the param defaults to "orted".
3. added a PLM base function that processes the orte_launch_agent value and adds the contents to a provided argv array. This can subsequently be harvested at-will to handle multi-word values
4. modified the PLMs to use this new function. All the PLMs except for the rsh PLM required very minor change - just called the function and moved on. The rsh PLM required much larger changes as - because of the rsh/ssh cmd line limitations - we had to correctly prepend any provided prefix to the correct argv entry.
5. added a new opal_argv_join_range function that allows the caller to "join" argv entries between two specified indices
Please let me know of any problems. I tried to make this as clean as possible, but cannot compile all PLMs to ensure all is correct.
This commit was SVN r19097.
2008-07-30 22:26:24 +04:00
|
|
|
int argc = 0;
|
2005-08-19 20:49:59 +04:00
|
|
|
int rc;
|
2008-12-09 03:32:04 +03:00
|
|
|
bool connected = false;
|
2008-02-28 04:57:57 +03:00
|
|
|
orte_std_cntr_t launched = 0, i;
|
2006-05-16 18:14:12 +04:00
|
|
|
char *bin_base = NULL, *lib_base = NULL;
|
2008-12-09 03:32:04 +03:00
|
|
|
tm_event_t *tm_events = NULL;
|
|
|
|
tm_task_id *tm_task_ids = NULL;
|
2006-09-15 01:29:51 +04:00
|
|
|
int local_err;
|
2008-12-09 03:32:04 +03:00
|
|
|
tm_event_t event;
|
2007-04-25 00:53:54 +04:00
|
|
|
bool failed_launch = true;
|
2007-08-14 22:44:52 +04:00
|
|
|
mode_t current_umask;
|
Fix a potential, albeit perhaps esoteric, race condition that can occur for fast HNP's, slow orteds, and fast apps. Under those conditions, it is possible for the orted to be caught in its original send of contact info back to the HNP, and thus for the progress stack never to recover back to a high level. In those circumstances, the orted can "hang" when trying to exit.
Add a new function to opal_progress that tells us our recursion depth to support that solution.
Yes, I know this sounds picky, but good ol' Jeff managed to make it happen by driving his cluster near to death...
Also ensure that we declare "failed" for the daemon job when daemons fail instead of the application job. This is important so that orte knows that it cannot use xcast to tell daemons to "exit", nor should it expect all daemons to respond. Otherwise, it is possible to hang.
After lots of testing, decide to default (again) to slurm detecting failed orteds. This proved necessary to avoid rather annoying hangs that were difficult to recover from. There are conditions where slurm will fail to launch all daemons (slurm folks are working on it), and yet again, good ol' Jeff managed to find both of them.
Thanks you Jeff! :-/
This commit was SVN r18611.
2008-06-06 23:36:27 +04:00
|
|
|
orte_jobid_t failed_job;
|
2008-11-20 21:57:35 +03:00
|
|
|
|
2009-01-08 17:27:52 +03:00
|
|
|
/* if we are timing, record the start time */
|
|
|
|
if (orte_timing) {
|
|
|
|
gettimeofday(&orte_plm_globals.daemonlaunchstart, NULL);
|
|
|
|
}
|
|
|
|
|
Fix a potential, albeit perhaps esoteric, race condition that can occur for fast HNP's, slow orteds, and fast apps. Under those conditions, it is possible for the orted to be caught in its original send of contact info back to the HNP, and thus for the progress stack never to recover back to a high level. In those circumstances, the orted can "hang" when trying to exit.
Add a new function to opal_progress that tells us our recursion depth to support that solution.
Yes, I know this sounds picky, but good ol' Jeff managed to make it happen by driving his cluster near to death...
Also ensure that we declare "failed" for the daemon job when daemons fail instead of the application job. This is important so that orte knows that it cannot use xcast to tell daemons to "exit", nor should it expect all daemons to respond. Otherwise, it is possible to hang.
After lots of testing, decide to default (again) to slurm detecting failed orteds. This proved necessary to avoid rather annoying hangs that were difficult to recover from. There are conditions where slurm will fail to launch all daemons (slurm folks are working on it), and yet again, good ol' Jeff managed to find both of them.
Thanks you Jeff! :-/
This commit was SVN r18611.
2008-06-06 23:36:27 +04:00
|
|
|
/* default to declaring the daemons as failed */
|
|
|
|
failed_job = ORTE_PROC_MY_NAME->jobid;
|
2008-12-09 03:32:04 +03:00
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
/* create a jobid for this job */
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_plm_base_create_jobid(&jdata->jobid))) {
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
goto cleanup;
|
|
|
|
}
|
|
|
|
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s plm:tm: launching job %s",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
ORTE_JOBID_PRINT(jdata->jobid)));
|
|
|
|
|
|
|
|
/* setup the job */
|
|
|
|
if (ORTE_SUCCESS != (rc = orte_plm_base_setup_job(jdata))) {
|
2006-11-16 18:11:45 +03:00
|
|
|
ORTE_ERROR_LOG(rc);
|
2007-04-25 00:53:54 +04:00
|
|
|
goto cleanup;
|
2005-08-19 20:49:59 +04:00
|
|
|
}
|
2008-02-28 04:57:57 +03:00
|
|
|
|
|
|
|
/* Get the map for this job */
|
|
|
|
if (NULL == (map = orte_rmaps.get_job_map(jdata->jobid))) {
|
|
|
|
ORTE_ERROR_LOG(ORTE_ERR_NOT_FOUND);
|
|
|
|
rc = ORTE_ERR_NOT_FOUND;
|
|
|
|
goto cleanup;
|
|
|
|
}
|
|
|
|
apps = (orte_app_context_t**)jdata->apps->addr;
|
|
|
|
nodes = (orte_node_t**)map->nodes->addr;
|
2005-03-14 23:57:21 +03:00
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
if (0 == map->num_new_daemons) {
|
2007-07-12 23:53:18 +04:00
|
|
|
/* have all the daemons we need - launch app */
|
|
|
|
goto launch_apps;
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
|
|
|
|
2008-12-09 03:32:04 +03:00
|
|
|
/* Allocate a bunch of TM events to use for tm_spawn()ing */
|
|
|
|
tm_events = malloc(sizeof(tm_event_t) * map->num_new_daemons);
|
|
|
|
if (NULL == tm_events) {
|
|
|
|
rc = ORTE_ERR_OUT_OF_RESOURCE;
|
|
|
|
ORTE_ERROR_LOG(rc);
|
2006-07-15 02:04:41 +04:00
|
|
|
goto cleanup;
|
|
|
|
}
|
2008-12-09 03:32:04 +03:00
|
|
|
tm_task_ids = malloc(sizeof(tm_task_id) * map->num_new_daemons);
|
2008-11-20 21:57:35 +03:00
|
|
|
if (NULL == tm_task_ids) {
|
2008-12-09 03:32:04 +03:00
|
|
|
rc = ORTE_ERR_OUT_OF_RESOURCE;
|
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
goto cleanup;
|
2008-11-20 21:57:35 +03:00
|
|
|
}
|
2006-07-15 02:04:41 +04:00
|
|
|
|
2005-08-19 20:49:59 +04:00
|
|
|
/* add the daemon command (as specified by user) */
|
Per the July technical meeting:
Standardize the handling of the orte launch agent option across PLMs. This has been a consistent complaint I have received - each PLM would register its own MCA param to get input on the launch agent for remote nodes (in fact, one or two didn't, but most did). This would then get handled in various and contradictory ways.
Some PLMs would accept only a one-word input. Others accepted multi-word args such as "valgrind orted", but then some would error by putting any prefix specified on the cmd line in front of the incorrect argument.
For example, while using the rsh launcher, if you specified "valgrind orted" as your launch agent and had "--prefix foo" on you cmd line, you would attempt to execute "ssh foo/valgrind orted" - which obviously wouldn't work.
This was all -very- confusing to users, who had to know which PLM was being used so they could even set the right mca param in the first place! And since we don't warn about non-recognized or non-used mca params, half of the time they would wind up not doing what they thought they were telling us to do.
To solve this problem, we did the following:
1. removed all mca params from the individual plms for the launch agent
2. added a new mca param "orte_launch_agent" for this purpose. To further simplify for users, this comes with a new cmd line option "--launch-agent" that can take a multi-word string argument. The value of the param defaults to "orted".
3. added a PLM base function that processes the orte_launch_agent value and adds the contents to a provided argv array. This can subsequently be harvested at-will to handle multi-word values
4. modified the PLMs to use this new function. All the PLMs except for the rsh PLM required very minor change - just called the function and moved on. The rsh PLM required much larger changes as - because of the rsh/ssh cmd line limitations - we had to correctly prepend any provided prefix to the correct argv entry.
5. added a new opal_argv_join_range function that allows the caller to "join" argv entries between two specified indices
Please let me know of any problems. I tried to make this as clean as possible, but cannot compile all PLMs to ensure all is correct.
This commit was SVN r19097.
2008-07-30 22:26:24 +04:00
|
|
|
orte_plm_base_setup_orted_cmd(&argc, &argv);
|
2005-08-19 20:49:59 +04:00
|
|
|
|
2007-04-10 18:23:32 +04:00
|
|
|
/* Add basic orted command line options */
|
2008-02-28 04:57:57 +03:00
|
|
|
orte_plm_base_orted_append_basic_args(&argc, &argv, "env",
|
|
|
|
&proc_vpid_index,
|
2008-06-03 01:46:34 +04:00
|
|
|
true);
|
2005-08-19 20:49:59 +04:00
|
|
|
|
2008-06-09 18:53:58 +04:00
|
|
|
if (0 < opal_output_get_verbosity(orte_plm_globals.output)) {
|
2005-08-19 20:49:59 +04:00
|
|
|
param = opal_argv_join(argv, ' ');
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s plm:tm: final top-level argv:\n\t%s",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
(NULL == param) ? "NULL" : param));
|
|
|
|
if (NULL != param) free(param);
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
2005-03-18 06:43:59 +03:00
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
rc = plm_tm_connect();
|
2005-08-19 20:49:59 +04:00
|
|
|
if (ORTE_SUCCESS != rc) {
|
|
|
|
goto cleanup;
|
2005-03-18 06:43:59 +03:00
|
|
|
}
|
2005-08-19 22:10:37 +04:00
|
|
|
connected = true;
|
2005-03-18 06:43:59 +03:00
|
|
|
|
2006-05-16 18:14:12 +04:00
|
|
|
/* Figure out the basenames for the libdir and bindir. There is a
|
2008-02-28 04:57:57 +03:00
|
|
|
lengthy comment about this in plm_rsh_module.c explaining all
|
2006-05-16 18:14:12 +04:00
|
|
|
the rationale for how / why we're doing this. */
|
2007-04-21 04:15:05 +04:00
|
|
|
lib_base = opal_basename(opal_install_dirs.libdir);
|
|
|
|
bin_base = opal_basename(opal_install_dirs.bindir);
|
2006-05-16 18:14:12 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* setup environment */
|
2008-06-24 02:39:36 +04:00
|
|
|
env = opal_argv_copy(orte_launch_environ);
|
2006-10-07 19:45:24 +04:00
|
|
|
|
2007-08-14 22:44:52 +04:00
|
|
|
/* add our umask -- see big note in orted.c */
|
|
|
|
current_umask = umask(0);
|
|
|
|
umask(current_umask);
|
|
|
|
asprintf(&var, "0%o", current_umask);
|
|
|
|
opal_setenv("ORTE_DAEMON_UMASK_VALUE", var, true, &env);
|
2007-08-15 01:12:00 +04:00
|
|
|
free(var);
|
2006-10-20 20:50:13 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* If we have a prefix, then modify the PATH and
|
|
|
|
LD_LIBRARY_PATH environment variables. We only allow
|
|
|
|
a single prefix to be specified. Since there will
|
|
|
|
always be at least one app_context, we take it from
|
|
|
|
there
|
|
|
|
*/
|
2008-02-28 04:57:57 +03:00
|
|
|
if (NULL != apps[0]->prefix_dir) {
|
2006-10-07 19:45:24 +04:00
|
|
|
char *newenv;
|
|
|
|
|
|
|
|
for (i = 0; NULL != env && NULL != env[i]; ++i) {
|
|
|
|
/* Reset PATH */
|
|
|
|
if (0 == strncmp("PATH=", env[i], 5)) {
|
|
|
|
asprintf(&newenv, "%s/%s:%s",
|
2008-02-28 04:57:57 +03:00
|
|
|
apps[0]->prefix_dir, bin_base, env[i] + 5);
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s plm:tm: resetting PATH: %s",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
newenv));
|
2006-10-07 19:45:24 +04:00
|
|
|
opal_setenv("PATH", newenv, true, &env);
|
|
|
|
free(newenv);
|
|
|
|
}
|
2005-10-02 15:58:18 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* Reset LD_LIBRARY_PATH */
|
|
|
|
else if (0 == strncmp("LD_LIBRARY_PATH=", env[i], 16)) {
|
|
|
|
asprintf(&newenv, "%s/%s:%s",
|
2008-02-28 04:57:57 +03:00
|
|
|
apps[0]->prefix_dir, lib_base, env[i] + 16);
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s plm:tm: resetting LD_LIBRARY_PATH: %s",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
newenv));
|
2006-10-07 19:45:24 +04:00
|
|
|
opal_setenv("LD_LIBRARY_PATH", newenv, true, &env);
|
|
|
|
free(newenv);
|
|
|
|
}
|
2005-10-02 15:58:18 +04:00
|
|
|
}
|
2006-10-07 19:45:24 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
/* Iterate through each of the nodes and spin
|
|
|
|
* up a daemon.
|
|
|
|
*/
|
2008-02-28 04:57:57 +03:00
|
|
|
for (i = 0; i < map->num_nodes; i++) {
|
|
|
|
orte_node_t* node = nodes[i];
|
|
|
|
char* vpid_string;
|
2006-07-05 00:12:35 +04:00
|
|
|
|
2007-06-14 16:33:34 +04:00
|
|
|
/* if this daemon already exists, don't launch it! */
|
2008-02-28 04:57:57 +03:00
|
|
|
if (node->daemon_launched) {
|
2007-06-14 16:33:34 +04:00
|
|
|
continue;
|
|
|
|
}
|
2007-07-12 23:53:18 +04:00
|
|
|
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s plm:tm: launching on node %s",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
node->name));
|
2006-10-07 19:45:24 +04:00
|
|
|
|
|
|
|
/* setup process name */
|
2008-02-28 04:57:57 +03:00
|
|
|
rc = orte_util_convert_vpid_to_string(&vpid_string, nodes[i]->daemon->name.vpid);
|
2006-10-07 19:45:24 +04:00
|
|
|
if (ORTE_SUCCESS != rc) {
|
2008-06-09 18:53:58 +04:00
|
|
|
opal_output(0, "plm:tm: unable to get daemon vpid as string");
|
2008-12-09 03:32:04 +03:00
|
|
|
exit(-1);
|
2006-10-07 19:45:24 +04:00
|
|
|
}
|
2008-02-28 04:57:57 +03:00
|
|
|
free(argv[proc_vpid_index]);
|
|
|
|
argv[proc_vpid_index] = strdup(vpid_string);
|
|
|
|
free(vpid_string);
|
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* exec the daemon */
|
2008-06-09 18:53:58 +04:00
|
|
|
if (0 < opal_output_get_verbosity(orte_plm_globals.output)) {
|
2006-10-07 19:45:24 +04:00
|
|
|
param = opal_argv_join(argv, ' ');
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s plm:tm: executing:\n\t%s",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
(NULL == param) ? "NULL" : param));
|
|
|
|
if (NULL != param) free(param);
|
2005-03-18 06:43:59 +03:00
|
|
|
}
|
2006-10-07 19:45:24 +04:00
|
|
|
|
2008-12-09 03:32:04 +03:00
|
|
|
rc = tm_spawn(argc, argv, env, node->launch_id, tm_task_ids + launched, tm_events + launched);
|
2007-02-09 18:06:45 +03:00
|
|
|
if (TM_SUCCESS != rc) {
|
This commit represents a bunch of work on a Mercurial side branch. As
such, the commit message back to the master SVN repository is fairly
long.
= ORTE Job-Level Output Messages =
Add two new interfaces that should be used for all new code throughout
the ORTE and OMPI layers (we already make the search-and-replace on
the existing ORTE / OMPI layers):
* orte_output(): (and corresponding friends ORTE_OUTPUT,
orte_output_verbose, etc.) This function sends the output directly
to the HNP for processing as part of a job-specific output
channel. It supports all the same outputs as opal_output()
(syslog, file, stdout, stderr), but for stdout/stderr, the output
is sent to the HNP for processing and output. More on this below.
* orte_show_help(): This function is a drop-in-replacement for
opal_show_help(), with two differences in functionality:
1. the rendered text help message output is sent to the HNP for
display (rather than outputting directly into the process' stderr
stream)
1. the HNP detects duplicate help messages and does not display them
(so that you don't see the same error message N times, once from
each of your N MPI processes); instead, it counts "new" instances
of the help message and displays a message every ~5 seconds when
there are new ones ("I got X new copies of the help message...")
opal_show_help and opal_output still exist, but they only output in
the current process. The intent for the new orte_* functions is that
they can apply job-level intelligence to the output. As such, we
recommend that all new ORTE and OMPI code use the new orte_*
functions, not thei opal_* functions.
=== New code ===
For ORTE and OMPI programmers, here's what you need to do differently
in new code:
* Do not include opal/util/show_help.h or opal/util/output.h.
Instead, include orte/util/output.h (this one header file has
declarations for both the orte_output() series of functions and
orte_show_help()).
* Effectively s/opal_output/orte_output/gi throughout your code.
Note that orte_output_open() takes a slightly different argument
list (as a way to pass data to the filtering stream -- see below),
so you if explicitly call opal_output_open(), you'll need to
slightly adapt to the new signature of orte_output_open().
* Literally s/opal_show_help/orte_show_help/. The function signature
is identical.
=== Notes ===
* orte_output'ing to stream 0 will do similar to what
opal_output'ing did, so leaving a hard-coded "0" as the first
argument is safe.
* For systems that do not use ORTE's RML or the HNP, the effect of
orte_output_* and orte_show_help will be identical to their opal
counterparts (the additional information passed to
orte_output_open() will be lost!). Indeed, the orte_* functions
simply become trivial wrappers to their opal_* counterparts. Note
that we have not tested this; the code is simple but it is quite
possible that we mucked something up.
= Filter Framework =
Messages sent view the new orte_* functions described above and
messages output via the IOF on the HNP will now optionally be passed
through a new "filter" framework before being output to
stdout/stderr. The "filter" OPAL MCA framework is intended to allow
preprocessing to messages before they are sent to their final
destinations. The first component that was written in the filter
framework was to create an XML stream, segregating all the messages
into different XML tags, etc. This will allow 3rd party tools to read
the stdout/stderr from the HNP and be able to know exactly what each
text message is (e.g., a help message, another OMPI infrastructure
message, stdout from the user process, stderr from the user process,
etc.).
Filtering is not active by default. Filter components must be
specifically requested, such as:
{{{
$ mpirun --mca filter xml ...
}}}
There can only be one filter component active.
= New MCA Parameters =
The new functionality described above introduces two new MCA
parameters:
* '''orte_base_help_aggregate''': Defaults to 1 (true), meaning that
help messages will be aggregated, as described above. If set to 0,
all help messages will be displayed, even if they are duplicates
(i.e., the original behavior).
* '''orte_base_show_output_recursions''': An MCA parameter to help
debug one of the known issues, described below. It is likely that
this MCA parameter will disappear before v1.3 final.
= Known Issues =
* The XML filter component is not complete. The current output from
this component is preliminary and not real XML. A bit more work
needs to be done to configure.m4 search for an appropriate XML
library/link it in/use it at run time.
* There are possible recursion loops in the orte_output() and
orte_show_help() functions -- e.g., if RML send calls orte_output()
or orte_show_help(). We have some ideas how to fix these, but
figured that it was ok to commit before feature freeze with known
issues. The code currently contains sub-optimal workarounds so
that this will not be a problem, but it would be good to actually
solve the problem rather than have hackish workarounds before v1.3 final.
This commit was SVN r18434.
2008-05-14 00:00:55 +04:00
|
|
|
orte_show_help("help-plm-tm.txt", "tm-spawn-failed",
|
2008-02-28 04:57:57 +03:00
|
|
|
true, argv[0], node->name, node->launch_id);
|
2007-04-25 00:53:54 +04:00
|
|
|
rc = ORTE_ERROR;
|
2006-10-07 19:45:24 +04:00
|
|
|
goto cleanup;
|
|
|
|
}
|
2007-04-25 00:53:54 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
launched++;
|
2007-07-12 23:53:18 +04:00
|
|
|
|
2006-10-07 19:45:24 +04:00
|
|
|
/* Allow some progress to occur */
|
|
|
|
opal_event_loop(OPAL_EVLOOP_NONBLOCK);
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
2008-02-28 04:57:57 +03:00
|
|
|
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s plm:tm:launch: finished spawning orteds",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME)));
|
2006-07-05 00:12:35 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
/* TM poll for all the spawns */
|
2008-12-09 03:32:04 +03:00
|
|
|
for (i = 0; i < launched; ++i) {
|
|
|
|
rc = tm_poll(TM_NULL_EVENT, &event, 1, &local_err);
|
2006-09-15 01:29:51 +04:00
|
|
|
if (TM_SUCCESS != rc) {
|
2008-12-09 03:32:04 +03:00
|
|
|
errno = local_err;
|
|
|
|
opal_output(0, "plm:tm: failed to poll for a spawned daemon, return status = %d", rc);
|
2007-04-25 00:53:54 +04:00
|
|
|
goto cleanup;
|
2005-08-19 20:49:59 +04:00
|
|
|
}
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
|
2008-06-03 01:46:34 +04:00
|
|
|
/* set a timer to tell us if one or more daemon's fails to start - use the
|
|
|
|
* millisec/daemon timeout provided by the user to compute time
|
|
|
|
*/
|
|
|
|
if (0 < orte_startup_timeout) {
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-06-03 01:46:34 +04:00
|
|
|
"%s plm:tm: setting startup timer for %d milliseconds",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
orte_startup_timeout));
|
|
|
|
ORTE_DETECT_TIMEOUT(&ev, map->num_new_daemons,
|
|
|
|
orte_startup_timeout*1000,
|
|
|
|
-1, failed_start);
|
|
|
|
}
|
|
|
|
|
2007-07-12 23:53:18 +04:00
|
|
|
/* wait for daemons to callback */
|
2008-02-28 04:57:57 +03:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_plm_base_daemon_callback(map->num_new_daemons))) {
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s plm:tm: daemon launch failed for job %s on error %s",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
ORTE_JOBID_PRINT(jdata->jobid), ORTE_ERROR_NAME(rc)));
|
2007-07-12 23:53:18 +04:00
|
|
|
goto cleanup;
|
|
|
|
}
|
|
|
|
|
2008-06-03 01:46:34 +04:00
|
|
|
/* if issued, cancel the failed-to-start timer */
|
|
|
|
if (NULL != ev) {
|
|
|
|
opal_event_del(ev);
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
}
|
|
|
|
|
2008-03-27 18:17:53 +03:00
|
|
|
launch_apps:
|
Fix a potential, albeit perhaps esoteric, race condition that can occur for fast HNP's, slow orteds, and fast apps. Under those conditions, it is possible for the orted to be caught in its original send of contact info back to the HNP, and thus for the progress stack never to recover back to a high level. In those circumstances, the orted can "hang" when trying to exit.
Add a new function to opal_progress that tells us our recursion depth to support that solution.
Yes, I know this sounds picky, but good ol' Jeff managed to make it happen by driving his cluster near to death...
Also ensure that we declare "failed" for the daemon job when daemons fail instead of the application job. This is important so that orte knows that it cannot use xcast to tell daemons to "exit", nor should it expect all daemons to respond. Otherwise, it is possible to hang.
After lots of testing, decide to default (again) to slurm detecting failed orteds. This proved necessary to avoid rather annoying hangs that were difficult to recover from. There are conditions where slurm will fail to launch all daemons (slurm folks are working on it), and yet again, good ol' Jeff managed to find both of them.
Thanks you Jeff! :-/
This commit was SVN r18611.
2008-06-06 23:36:27 +04:00
|
|
|
/* since the daemons have launched, any failures now will be for the
|
|
|
|
* application job
|
|
|
|
*/
|
|
|
|
failed_job = jdata->jobid;
|
2008-03-27 18:17:53 +03:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_plm_base_launch_apps(jdata->jobid))) {
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-03-27 18:17:53 +03:00
|
|
|
"%s plm:tm: launch of apps failed for job %s on error %s",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME),
|
|
|
|
ORTE_JOBID_PRINT(jdata->jobid), ORTE_ERROR_NAME(rc)));
|
|
|
|
goto cleanup;
|
|
|
|
}
|
|
|
|
|
|
|
|
/* if we get here, then everything launched okay - record that fact */
|
|
|
|
failed_launch = false;
|
|
|
|
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
|
2006-07-05 00:12:35 +04:00
|
|
|
cleanup:
|
2007-04-25 00:53:54 +04:00
|
|
|
if (NULL != argv) {
|
|
|
|
opal_argv_free(argv);
|
|
|
|
}
|
|
|
|
if (NULL != env) {
|
|
|
|
opal_argv_free(env);
|
|
|
|
}
|
2006-10-08 02:44:00 +04:00
|
|
|
|
2008-12-09 03:32:04 +03:00
|
|
|
if (connected) {
|
|
|
|
plm_tm_disconnect();
|
|
|
|
}
|
|
|
|
if (NULL != tm_events) {
|
|
|
|
free(tm_events);
|
|
|
|
}
|
|
|
|
if (NULL != tm_task_ids) {
|
|
|
|
free(tm_task_ids);
|
|
|
|
}
|
|
|
|
|
2006-05-16 18:14:12 +04:00
|
|
|
if (NULL != lib_base) {
|
|
|
|
free(lib_base);
|
|
|
|
}
|
|
|
|
if (NULL != bin_base) {
|
|
|
|
free(bin_base);
|
|
|
|
}
|
|
|
|
|
2007-04-25 00:53:54 +04:00
|
|
|
/* check for failed launch - if so, force terminate */
|
|
|
|
if (failed_launch) {
|
2008-12-09 03:32:04 +03:00
|
|
|
orte_plm_base_launch_failed(failed_job, -1, ORTE_ERROR_DEFAULT_EXIT_CODE, ORTE_JOB_STATE_FAILED_TO_START);
|
2006-09-15 01:29:51 +04:00
|
|
|
}
|
2007-04-25 00:53:54 +04:00
|
|
|
|
2008-06-03 01:46:34 +04:00
|
|
|
/* setup a "heartbeat" timer to periodically check on
|
|
|
|
* the state-of-health of the orteds, if requested AND
|
|
|
|
* we actually launched some daemons!
|
|
|
|
*/
|
|
|
|
if (0 < map->num_new_daemons) {
|
|
|
|
orte_plm_base_start_heart();
|
Bring the timing instrumentation to the trunk.
If you want to look at our launch and MPI process startup times, you can do so with two MCA params:
OMPI_MCA_orte_timing: set it to anything non-zero and you will get the launch time for different steps in the job launch procedure. The degree of detail depends on the launch environment. rsh will provide you with the average, min, and max launch time for the daemons. SLURM block launches the daemon, so you only get the time to launch the daemons and the total time to launch the job. Ditto for bproc. TM looks more like rsh. Only those four environments are currently supported - anyone interested in extending this capability to other environs is welcome to do so. In all cases, you also get the time to setup the job for launch.
OMPI_MCA_ompi_timing: set it to anything non-zero and you will get the time for mpi_init to reach the compound registry command, the time to execute that command, the time to go from our stage1 barrier to the stage2 barrier, and the time to go from the stage2 barrier to the end of mpi_init. This will be output for each process, so you'll have to compile any statistics on your own. Note: if someone develops a nice parser to do so, it would be really appreciated if you could/would share!
This commit was SVN r12302.
2006-10-25 19:27:47 +04:00
|
|
|
}
|
|
|
|
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-02-28 04:57:57 +03:00
|
|
|
"%s plm:tm:launch: finished",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME)));
|
|
|
|
|
2005-08-19 20:49:59 +04:00
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
static int plm_tm_terminate_job(orte_jobid_t jobid)
|
2005-08-19 20:49:59 +04:00
|
|
|
{
|
2006-09-15 01:29:51 +04:00
|
|
|
int rc;
|
|
|
|
|
2007-04-25 00:53:54 +04:00
|
|
|
/* order all of the daemons to kill their local procs for this job */
|
2008-02-28 04:57:57 +03:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_plm_base_orted_kill_local_procs(jobid))) {
|
2006-09-15 01:29:51 +04:00
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
2007-04-25 00:53:54 +04:00
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
return rc;
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2006-09-15 01:29:51 +04:00
|
|
|
/**
|
|
|
|
* Terminate the orteds for a given job
|
|
|
|
*/
|
2008-02-28 04:57:57 +03:00
|
|
|
int plm_tm_terminate_orteds(void)
|
2006-09-15 01:29:51 +04:00
|
|
|
{
|
|
|
|
int rc;
|
|
|
|
|
2008-12-09 03:32:04 +03:00
|
|
|
/* now tell them to die! */
|
2008-12-09 16:31:33 +03:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_plm_base_orted_exit(ORTE_DAEMON_EXIT_WITH_REPLY_CMD))) {
|
2006-09-15 01:29:51 +04:00
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
return rc;
|
|
|
|
}
|
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
static int plm_tm_signal_job(orte_jobid_t jobid, int32_t signal)
|
2006-06-08 22:27:17 +04:00
|
|
|
{
|
2006-09-15 01:29:51 +04:00
|
|
|
int rc;
|
|
|
|
|
|
|
|
/* order them to pass this signal to their local procs */
|
2008-02-28 04:57:57 +03:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_plm_base_orted_signal_local_procs(jobid, signal))) {
|
2006-09-15 01:29:51 +04:00
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
|
|
|
|
|
|
|
return rc;
|
2006-06-08 22:27:17 +04:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2005-03-14 23:57:21 +03:00
|
|
|
/*
|
|
|
|
* Free stuff
|
|
|
|
*/
|
2008-02-28 04:57:57 +03:00
|
|
|
static int plm_tm_finalize(void)
|
2005-03-14 23:57:21 +03:00
|
|
|
{
|
2006-09-15 01:29:51 +04:00
|
|
|
int rc;
|
|
|
|
|
2005-08-19 20:49:59 +04:00
|
|
|
/* cleanup any pending recvs */
|
2008-02-28 04:57:57 +03:00
|
|
|
if (ORTE_SUCCESS != (rc = orte_plm_base_comm_stop())) {
|
2006-09-15 01:29:51 +04:00
|
|
|
ORTE_ERROR_LOG(rc);
|
|
|
|
}
|
2005-03-14 23:57:21 +03:00
|
|
|
|
|
|
|
return ORTE_SUCCESS;
|
|
|
|
}
|
|
|
|
|
|
|
|
|
2008-02-28 04:57:57 +03:00
|
|
|
static int plm_tm_connect(void)
|
2005-03-14 23:57:21 +03:00
|
|
|
{
|
2005-08-19 20:49:59 +04:00
|
|
|
int ret;
|
|
|
|
struct tm_roots tm_root;
|
|
|
|
int count, progress;
|
|
|
|
|
|
|
|
/* try a couple times to connect - might get busy signals every
|
|
|
|
now and then */
|
|
|
|
for (count = 0 ; count < 10; ++count) {
|
|
|
|
ret = tm_init(NULL, &tm_root);
|
|
|
|
if (TM_SUCCESS == ret) {
|
|
|
|
return ORTE_SUCCESS;
|
|
|
|
}
|
2005-03-14 23:57:21 +03:00
|
|
|
|
2005-08-19 20:49:59 +04:00
|
|
|
for (progress = 0 ; progress < 10 ; ++progress) {
|
|
|
|
opal_progress();
|
|
|
|
#if HAVE_SCHED_YIELD
|
|
|
|
sched_yield();
|
|
|
|
#endif
|
|
|
|
}
|
|
|
|
}
|
2005-03-14 23:57:21 +03:00
|
|
|
|
2005-08-19 20:49:59 +04:00
|
|
|
return ORTE_ERR_RESOURCE_BUSY;
|
2005-03-14 23:57:21 +03:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2008-12-09 03:32:04 +03:00
|
|
|
static int plm_tm_disconnect(void)
|
|
|
|
{
|
|
|
|
tm_finalize();
|
|
|
|
|
|
|
|
return ORTE_SUCCESS;
|
|
|
|
}
|
|
|
|
|
2008-06-03 01:46:34 +04:00
|
|
|
/* call this function if the timer fires indicating that one
|
|
|
|
* or more daemons failed to start
|
|
|
|
*/
|
|
|
|
static void failed_start(int fd, short dummy, void *arg)
|
|
|
|
{
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-06-03 01:46:34 +04:00
|
|
|
"%s plm:tm:failed_start",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME)));
|
|
|
|
|
|
|
|
/* if we are aborting, ignore this */
|
|
|
|
if (orte_abnormal_term_ordered) {
|
2008-06-09 18:53:58 +04:00
|
|
|
OPAL_OUTPUT_VERBOSE((1, orte_plm_globals.output,
|
2008-06-03 01:46:34 +04:00
|
|
|
"%s plm:tm:failed_start - abnormal term in progress",
|
|
|
|
ORTE_NAME_PRINT(ORTE_PROC_MY_NAME)));
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
2008-06-07 02:53:43 +04:00
|
|
|
orte_plm_base_launch_failed(ORTE_PROC_MY_NAME->jobid, -1,
|
2008-06-03 01:46:34 +04:00
|
|
|
ORTE_ERROR_DEFAULT_EXIT_CODE, ORTE_JOB_STATE_FAILED_TO_START);
|
|
|
|
}
|