There is no restriction to use the C/R functionality in Open MPI in a TM
environment (that I am aware of), if you use the ompi-checkpoint/ompi-restart
commands directly.
If you want TM to checkpoint/restart Open MPI processes for you as part of the
resource management role, then there is a bit
On Feb 21, 2011, at 12:50 AM, DOHERTY, Greg wrote:
> blcr needs cr_mpirun to start the job without torque support to be able
> to checkpoint the mpi job correctly.
Josh --
Do we have a restriction on BLCR support when used with TM?
--
Jeff Squyres
jsquy...@cisco.com
For corporate legal informa
Simplest soln: add -bynode to your mpirun cmd line
On Feb 20, 2011, at 10:50 PM, DOHERTY, Greg wrote:
> In order to be able to checkpoint openmpi jobs with blcr, we have
> configured openmpi as follows
>
> ./configure --prefix=/data1/packages/openmpi/1.5.1-blcr-without-tm
> --disable-openib-co
In order to be able to checkpoint openmpi jobs with blcr, we have
configured openmpi as follows
./configure --prefix=/data1/packages/openmpi/1.5.1-blcr-without-tm
--disable-openib-connectx-xrc --disable-openib-rdmacm --with-ft=cr
--enable-mpi-threads --enable-ft-thread --with-blcr=/usr
--with-blc