[mpich-discuss] mpi_comm_spawn - process not destroyed

[Stanislav Simko]

Hi Min,attached are configure and make logs for the build that I did
for myself on our local cluster with Intel compilers. I.e., build is
definitely not guaranteed to be perfect/optimal. But please keep in
mind that I get the same behaviour with standard MPICH package in
Fedora distribution - I think that configuration options should be
available online, maybe prepared by someone from MPICH?
Also, I tested with simple c++ hello world like program and it's the
same.
Thank you.best,stanislav.

On Sun, 2017-08-13 at 19:58 +0100, Min Si wrote:
>     Hi Stanislav,
> 
>     
> 
>     This seems interesting. Could you please also attach the MPICH
>     config.log ? You can find under the directory where you build
> MPICH.
>     I will look into this problem then and keep you updated.
> 
>     
> 
>     Min
> 
>     
> 
>     On 8/11/17 1:31 PM, Stanislav Simko
>       wrote:
> 
>     
>     
> >       
> >       Dear all,
> >       
> > 
> >       
> >       I'm just trying some very basic stuff with MPI_COMM_SPAWN in
> >         python (i.e. I use mpi4py package), but I see behaviour
> > that I
> >         do not understand - the child process gets spawned, does
> > its
> >         stuff and then "should" finish. I see though, that the
> > process
> >         created for the child stays alive. I see this only with the
> >         MPICH, OPENMPI does what I would (naively) expect. In this
> > way I
> >         can end up with N "ghost" process, after calling SPAWN N-
> > times.
> >         My minimal working example is following:
> >       
> > 
> >       
> >       
> > 
> >       
> >       ______________________________________________
> >       parent.py
> >       
> > 
> >       
> >       from __future__ import print_function
> >       from mpi4py import MPI
> >       comm = MPI.COMM_WORLD
> >       spawned =
> >         MPI.COMM_SELF.Spawn(sys.executable,args=['child.py'],maxpro
> > cs=1)
> >       print("parent process is waiting for child")
> >       spawned.Barrier()
> >       
> > 
> >       
> >       
> > 
> >       
> >       ______________________________________________
> >       child.py
> >       
> > 
> >       
> >       from __future__ import print_function
> >       from mpi4py import MPI
> >       parent = MPI.Comm.Get_parent()
> >       # just do some stupid stuff that takes a bit of time
> >       for i in range(5000000):
> >           a = i*i+1-(i*10) + math.sin(math.pow(i,i%8))
> >       parent.Barrier()
> >       
> > 
> >       
> >       ______________________________________________
> >       
> > 
> >       
> >       I run with e.g.:
> >       mpirun -n 1 python mpi.py
> >       
> > 
> >       
> >       Do I miss something with SPAWN method?
> >       (I tested on two independent systems, our local cluster with
> >         mpich v3.0.4, and my laptop - fedora 26, mpich v3.2.8 from
> >         repositories)
> >       
> > 
> >       
> >       thank you very much for suggestions.
> >       
> > 
> >       
> >       Regards,
> >       stanislav.
> >       
> >       
> >       
> > 
> >       
> >       
> > 
> >       _______________________________________________
> > discuss mailing list     discuss at mpich.org
> > To manage subscription options or unsubscribe:
> > https://lists.mpich.org/mailman/listinfo/discuss
> >     
> 
>     
> 
>   
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20170813/a65aea84/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.log
Type: text/x-log
Size: 424040 bytes
Desc: config.log
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20170813/a65aea84/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: config.status
Type: application/x-shellscript
Size: 118350 bytes
Desc: config.status
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20170813/a65aea84/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: make_error.log
Type: text/x-log
Size: 560 bytes
Desc: make_error.log
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20170813/a65aea84/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: make.log
Type: text/x-log
Size: 75754 bytes
Desc: make.log
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20170813/a65aea84/attachment-0003.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: configure.log
Type: text/x-log
Size: 97476 bytes
Desc: configure.log
URL: <http://lists.mpich.org/pipermail/discuss/attachments/20170813/a65aea84/attachment-0004.bin>
-------------- next part --------------
_______________________________________________
discuss mailing list     discuss at mpich.org
To manage subscription options or unsubscribe:
https://lists.mpich.org/mailman/listinfo/discuss