Open MPI logo

Open MPI User's Mailing List Archives

  |   Home   |   Support   |   FAQ   |  

This web mail archive is frozen.

This page is part of a frozen web archive of this mailing list.

You can still navigate around this archive, but know that no new mails have been added to it since July of 2016.

Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.

Subject: Re: [OMPI users] Checkpointing mpi4py program
From: Joshua Hursey (jjhursey_at_[hidden])
Date: 2010-08-09 16:37:58

I have not tried to checkpoint an mpi4py application, so I cannot say for sure if it works or not. You might be hitting something with the Python runtime interacting in an odd way with either Open MPI or BLCR.

Can you attach a debugger and get a backtrace on a stuck checkpoint? That might show us where things are held up.

-- Josh

On Aug 9, 2010, at 4:04 PM, <ananda.mudar_at_[hidden]> <ananda.mudar_at_[hidden]> wrote:

> Hi
> I have integrated mpi4py with openmpi 1.4.2 that was built with BLCR 0.8.2. When I run ompi-checkpoint on the program written using mpi4py, I see that program doesn’t resume sometimes after successful checkpoint creation. This doesn’t occur always meaning the program resumes after successful checkpoint creation most of the time and completes successfully. Has anyone tested the checkpoint/restart functionality with mpi4py programs? Are there any best practices that I should keep in mind while checkpointing mpi4py programs?
> Thanks for your time
> - Ananda
> 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
> users_at_[hidden]