On Thu, Mar 07, 2013 at 04:18:58PM -0600, Pavan Balaji wrote:
>
> This was already present in 1.5, though not enabled by default.
> However, there were some bug fixes in 3.0, so using the latest version
> is the best bet.
>
> -- Pavan
>
> On 03/07/2013 03:57 PM US Central Time, Dave Goodell wrote:
> > On Mar 7, 2013, at 3:51 PM CST, Bharath Ramesh <bramesh(a)vt.edu> wrote:
> >
> >> I am using mvapich2-1.9a2 which is based of mpich2-1.5. We have
> >> enabled Torque integration with hydra. We are noticing an issue
> >> where in Torque is not tracking the resource used by the MPI
> >> application when they are built with mvapich2. Further
> >> investigation revealed that mvapich2 hydra process launcher was
> >> not setting the correct session id to what torque used for
> >> forking the shell. I am wondering if this is a known issue or
> >> something that has already been fixed. If it has been fixed, what
> >> would be the best way to upgrade just hydra without affecting the
> >> rest of MPI stack.
> >
> > I can't speak to whether the issue is known or fixed (Pavan will know). But you can install a different version of Hydra from one of the release tarballs or nightly tarballs:
Sorry about a delayed response. I installed mvapich2-1.9b based
on mpich-3.0.2 and I can say that the issue still exists. To
better understand I am attaching the output of ps axf with
relevant portions to differentiate between the behavior of hydra
launcher when compared to OpenMPI which does the correct thing.
This allows torque to track the resources used.
--
Bharath
