Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

orte_snapc(7) [debian man page]

ORTE_SNAPC(7)							     Open MPI							     ORTE_SNAPC(7)

NAME

       ORTE_SNAPC  - Open RTE MCA Snapshot Coordination (SnapC) Framework: Overview of Open RTE's SnapC framework, and selected modules.  Open MPI
       1.4.5

DESCRIPTION

       Open RTE can coordinate the generation of a global snapshot of a parallel job from many distributed local snapshots. The components in this
       framework  determine how to: Initiate the checkpoint of the parallel application, gather together the many distributed local snapshots, and
       provide the user with a global snapshot handle reference that can be used to restart the parallel application.

GENERAL PROCESS REQUIREMENTS

       In order for a process to use the Open RTE SnapC components it must adhear to a few programmatic requirements.

       First, the program must call ORTE_INIT early in its execution. This should only be called once, and it is not possible  to  checkpoint  the
       process without it first having called this function.

       The program must call ORTE_FINALIZE before termination.

       A user may initiate a checkpoint of a parallel application by using the orte-checkpoint(1) and orte-restart(1) commands.

AVAILABLE COMPONENTS

       Open RTE ships with one SnapC component: full.

       The following MCA parameters apply to all components:

       snapc_base_verbose
	   Set the verbosity level for all components. Default is 0, or silent except on error.

       snapc_base_global_snapshot_dir
	   The directory to store the checkpoint snapshots. Default is /tmp.

   full SnapC Component
       The  full  component gathers together the local snapshots to the disk local to the Head Node Process (HNP) before completing the checkpoint
       of the process. This component does not currently support replicated HNPs, or timer based gathering of  local  snapshot	data.  This  is  a
       3-tiered hierarchy of coordinators.

       The full component has the following MCA parameters:

       snapc_full_priority
	   The component's priority to use when selecting the most appropriate component for a run.

       snapc_full_verbose
	   Set the verbosity level for this component. Default is 0, or silent except on error.

   none SnapC Component
       The none component simply selects no SnapC component. All of the SnapC function calls return immediately with ORTE_SUCCESS.

       This  component	is the last component to be selected by default. This means that if another component is available, and the none component
       was not explicity requested then ORTE will attempt to activate all of the available components before falling back to this component.

SEE ALSO

	 orte-checkpoint(1), orte-restart(1), opal-checkpoint(1), opal-restart(1), orte_filem(7), opal_crs(7)

1.4.5								   Feb 10, 2012 						     ORTE_SNAPC(7)

Check Out this Related Man Page

orte-clean(1)							     Open MPI							     orte-clean(1)

NAME

       orte-clean - Cleans up any stale processes and files leftover from Open MPI jobs.

SYNOPSIS

       orte-clean [--verbose]
       mpirun --pernode [--host | --hostfile file] orte-clean [--verbose]

OPTIONS

       [-v | --verbose] This argument will run the command in verbose mode and print out the universes that are getting cleaned up as well as pro-
       cesses that are being killed.

DESCRIPTION

       orte-clean attempts to clean up any processes and files left over from Open MPI jobs that were run in the past as  well	as  any  currently
       running jobs.  This includes OMPI infrastructure and helper commands, any processes that were spawned as part of the job, and any temporary
       files.  orte-clean will only act upon processes and files that belong to the user running the orte-clean command.  If run as root, it  will
       kill off processes belonging to any users.

       When run from the command line, orte-clean will attempt to clean up the local node it is run from.  When launched via mpirun, it will clean
       up the nodes selected by mpirun.

EXAMPLES

       Example 1: Clean up local node only.

       example% orte-clean

       Example 2: To clean up on a specific set of nodes specified on command line, it is recommended to use the pernode option.   This  will  run
       one orte-clean for each node.

       example% mpirun --pernode --host node1,node2,node3 orte-clean

       To clean up on a specific set of nodes from a file.

       example% mpirun --pernode --hostfile nodes_file orte-clean

       Example 3: Within a resource managed environment like N1GE, SLURM, or Torque.  The following example is from N1GE.

       First, we see that we have two nodes with two CPUs each.

       example% qsh -pe orte 4
       example% mpirun -np 4 hostname
       node1
       node1
       node2
       node2

       Clean up all the nodes in the cluster.

       example% mpirun --pernode orte-clean

       Clean up a subset of the nodes in the cluster.

       example% mpirun --pernode --host node1 orte-clean

SEE ALSO

       orterun(1), orte-ps(1)

1.4.5								   Feb 10, 2012 						     orte-clean(1)
Man Page