[gridengine users] Tight integration problem with mvapich2 2.0

Reuti reuti at staff.uni-marburg.de
Wed Jan 7 12:36:20 UTC 2015


> Am 07.01.2015 um 13:18 schrieb Götz Waschk <goetz.waschk at gmail.com>:
> Hi everyone,
> I have noticed one difference in the behaviour of mvapich2 between 1.8 and 2.0rc1: with the former, hydra_pmi_proxy and all mpi processes are in the same process group, but with the later version, they all have a different pgid. Just killing hydra_pmi_proxy will terminate all mpi processes with 1.8 but not with 2.0rc1.

Yes, the default is to kill the process group (done by a negative pid as argument). But you can try to use the additional group id to look for all kids:

$ qconf -sconf
execd_params                 ENABLE_ADDGRP_KILL=TRUE

-- Reuti

> Any idea to work around this?
> Regards, Götz
> _______________________________________________
> users mailing list
> users at gridengine.org
> https://gridengine.org/mailman/listinfo/users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 203 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://gridengine.org/pipermail/users/attachments/20150107/1e456b8b/attachment.sig>

More information about the users mailing list