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

OPAL-CHECKPOINT(1)						       1.4.5							OPAL-CHECKPOINT(1)

NAME

       opal-checkpoint - Checkpoint a running sequential process using the Open PAL Checkpoint/Restart Service (CRS).

       Note:  This should only be used by the user if the application being checkpointed is an OPAL-only application. If it is an Open RTE or Open
       MPI program their respective tools should be used.

SYNOPSIS

       opal-checkpoint [ options ] <PID>

Options
       opal-checkpoint will attempt to notify a running process that it has been requested that the process checkpoint itself. A  snapshot  handle
       reference is presented to the user, which is used in opal_restart to restart the process.

       <PID>	 Process ID of the running target process.

       -h | --help
		 Display help for this command

       --term	 After checkpointing the running process, terminate it.

       -v | --verbose
		 Enable verbose output for debugging.

       -n | --name
		 Request a specific name for the local snapshot reference.

       -w | --where
		 Request that the local snapshot reference be placed in a specific location.

       -gmca | --gmca <key> <value>
		 Pass global MCA parameters that are applicable to all contexts. <key> is the parameter name; <value> is the parameter value.

       -mca | --mca <key> <value>
		 Send arguments to various MCA modules.

DESCRIPTION

       opal-checkpoint	can  be invoked multiple, non-overlapping times. This allows the user to take involuntary checkpoints of a running sequen-
       tial process. See opal_crs(7) for more information about the CRS framework and components. It is convenient to note that the user does  not
       need to spectify the checkpointer to be used here, as that is determined completely by the running process being checkpointed.

SEE ALSO

	 opal-restart(1), opal_crs(7)

Open MPI							   Feb 10, 2012 						OPAL-CHECKPOINT(1)
Man Page