Re: [OMPI devel] MTT database

2017-10-12 Thread Josh Hursey
It looks like the AWS database is unreachable. From the dashboard it looks like we exhausted disk space, which might be the root cause. From the logs I can see on the Dashboard, it looks like the psql daemon failed to restart... I can free up database space, if I can attach to the server. I'm not

[OMPI devel] MTT database

2017-10-12 Thread Howard Pritchard
is anyone seeing issues with MTT today? When I go to the website and click on summary I get this back in my browser window: MTTDatabase abort: Could not connect to the ompidb database; submit this run later. Howard ___ devel mailing list

Re: [OMPI devel] OMPI devel] mpi_yield_when_idle=1 and still 100%CPU

2017-10-12 Thread Gilles Gouaillardet
Paul, Sorry for the typo. The patch was developed on the master branch. Note v1.10 is no more supported, and since passive wait is a new feature, it would start at v3.1 or later. That being said, if you are kind of stucked with 1.10.7, i can try to craft a one off patch in order to help

Re: [OMPI devel] mpi_yield_when_idle=1 and still 100%CPU

2017-10-12 Thread Paul Kapinos
Hi Gilles, Thank you for your message and quick path! You likely mean (instead of links in your eMail below) https://github.com/open-mpi/ompi/pull/4331 and https://github.com/open-mpi/ompi/pull/4331.patch for your PR #4331 (note '4331' instead of '4431' :-) I was not able to path 1.10.7 release

Re: [OMPI devel] mpi_yield_when_idle=1 and still 100%CPU

2017-10-12 Thread Gilles Gouaillardet
Paul, i made PR #4331 https://github.com/open-mpi/ompi/pull/4431 in order to implement this. in order to enable passive wait, you simply need to mpirun --mca mpi_poll_when_idle true ... fwiw, when you use mpi_yield_when_idle, Open MPI does (highly oversimplified) for (...)