The functionality of checkpoint operation is not tied to CPU
utilization. Are you running with the C/R thread enabled? If not then
the checkpoint might be waiting until the process enters the MPI
Does the system emit an error message describing the error that it
The C/R support does require that all processes be between MPI_INIT
and MPI_FINALIZE. It is difficult to guarantee that the job is between
these two functions globally (there are race conditions to worry
about). This might be causing the problem as well since if some of the
processes have not passed through MPI_INIT then some of the support
services might not be properly initialized.
Let me know what you find, and we can start looking at what might be
causing this problem.
On May 11, 2010, at 5:35 PM, wrote:
> I am using open-mpi 1.3.4 with BLCR. Sometimes I am running into a
> strange problem with ompi-checkpoint command. Even though I see that
> all MPI processes (equal to np argument) are running, ompi-
> checkpoint command fails at times. I have seen this failure always
> when the MPI processes spawned are not fully running ie; these
> processes are not running above 90% CPU utilization. How do I ensure
> that the MPI processes are fully up and running before I issue ompi-
> checkpoint because dynamically detecting if the processes are
> utilizing above 90% CPU resources is not easy.
> Are there any MCA parameters I can use to overcome this issue?
> Please do not print this email unless it is absolutely necessary.
> The information contained in this electronic message and any
> attachments to this message are intended for the exclusive use of
> the addressee(s) and may contain proprietary, confidential or
> privileged information. If you are not the intended recipient, you
> should not disseminate, distribute or copy this e-mail. Please
> notify the sender immediately and destroy all copies of this message
> and any attachments.
> WARNING: Computer viruses can be transmitted via email. The
> recipient should check this email and any attachments for the
> presence of viruses. The company accepts no liability for any damage
> caused by any virus transmitted by this email.
> users mailing list