{"action":"created","issue":{"url":"https://api.github.com/repos/raffenet/mpich-migrate-test/issues/317","repository_url":"https://api.github.com/repos/raffenet/mpich-migrate-test","labels_url":"https://api.github.com/repos/raffenet/mpich-migrate-test/issues/317/labels{/name}","comments_url":"https://api.github.com/repos/raffenet/mpich-migrate-test/issues/317/comments","events_url":"https://api.github.com/repos/raffenet/mpich-migrate-test/issues/317/events","html_url":"https://github.com/raffenet/mpich-migrate-test/issues/317","id":168418563,"number":317,"title":"The infamous 5-s delay bug...","user":{"login":"raffenet","id":1410792,"avatar_url":"https://avatars.githubusercontent.com/u/1410792?v=3","gravatar_id":"","url":"https://api.github.com/users/raffenet","html_url":"https://github.com/raffenet","followers_url":"https://api.github.com/users/raffenet/followers","following_url":"https://api.github.com/users/raffenet/following{/other_user}","gists_url":"https://api.github.com/users/raffenet/gists{/gist_id}","starred_url":"https://api.github.com/users/raffenet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/raffenet/subscriptions","organizations_url":"https://api.github.com/users/raffenet/orgs","repos_url":"https://api.github.com/users/raffenet/repos","events_url":"https://api.github.com/users/raffenet/events{/privacy}","received_events_url":"https://api.github.com/users/raffenet/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2016-07-29T21:29:54Z","updated_at":"2016-07-29T21:29:56Z","closed_at":null,"body":"**Originally by _Brian Dushaw <dushaw@apl.washington.edu>_ on 2008-12-03 02:48:26 -0600**\n\n___\n\n\n```\n\nDear MPICH-ers,\n   I have compiled and installed the latest mpich - 1.0.8 - on my\nSuse linux 10.3 x64 system.  I am writing to report that a bug (?) that\nwe talked about some time ago still seems to exist.\n   This is the annoying 5-s hang before an mpi job will finally\ncomplete.  All of the parallel jobs give their happy \"FORTRAN STOP\"s,\nbut then mpich hangs for 5 s before finally completing.  It does not\noccur all the time, but often enough to be annoying.  I forget the\ndetails, other than perhaps that the issue seemed to occur only on\nspecific systems.  The fix seems to be to edit one of the *.py\nscripts and change the \"timeout=5.0\" to \"timeout=0.1\", say.  I forget\nwhich script it is, alas.\n   I am running my code with:\n          time mpiexec -n 8 time ./mpiroutine < input.file\nif that makes a difference.\n\n   It has now been years and a few Suse upgrades since I first reported\nthe problem...ah hem.\n   (Although the problem was occurring regularly a few minutes ago,\nit doesn't seem to be occurring now...seems to be one of THOSE kind\nof things...  Well, I'll report it.)\n\nThanks,\n\nB.D.\n\n%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%\n\nBrian Dushaw\nApplied Physics Laboratory\nUniversity of Washington\n1013 N.E. 40th Street\nSeattle, WA  98105-6698\n(206) 685-4198   (206) 543-1300\n(206) 543-6785 (fax)\ndushaw@apl.washington.edu\n\nWeb Page:  http://faculty.washington.edu/dushaw/index.html\n```"},"comment":{"url":"https://api.github.com/repos/raffenet/mpich-migrate-test/issues/comments/236298556","html_url":"https://github.com/raffenet/mpich-migrate-test/issues/317#issuecomment-236298556","issue_url":"https://api.github.com/repos/raffenet/mpich-migrate-test/issues/317","id":236298556,"user":{"login":"raffenet","id":1410792,"avatar_url":"https://avatars.githubusercontent.com/u/1410792?v=3","gravatar_id":"","url":"https://api.github.com/users/raffenet","html_url":"https://github.com/raffenet","followers_url":"https://api.github.com/users/raffenet/followers","following_url":"https://api.github.com/users/raffenet/following{/other_user}","gists_url":"https://api.github.com/users/raffenet/gists{/gist_id}","starred_url":"https://api.github.com/users/raffenet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/raffenet/subscriptions","organizations_url":"https://api.github.com/users/raffenet/orgs","repos_url":"https://api.github.com/users/raffenet/repos","events_url":"https://api.github.com/users/raffenet/events{/privacy}","received_events_url":"https://api.github.com/users/raffenet/received_events","type":"User","site_admin":false},"created_at":"2016-07-29T21:29:55Z","updated_at":"2016-07-29T21:29:55Z","body":"**Originally by _Brian Dushaw_ on 2008-12-03 16:01:49 -0600**\n\n___\n```\n\nR.,\n   Thanks - that seems to have fixed the problem, stopgap style anyways.\nI did attempt to search these fora for the e-mail, but couldn't find it.\nI had forgotten about the problem when I upgraded mpich, and I foolishly\ndeleted the old installation which would have given me the clue.\n\nB.D.\n\nOn Wed, 3 Dec 2008, mpich2 wrote:\n\n> ------------------------------------------------------+---------------------\n>  Reporter:  Brian Dushaw <dushaw@apl.washington.edu>  |        Owner:\n>      Type:  bug                                       |       Status:  new\n>  Priority:  major                                     |    Milestone:\n> Component:  mpich2                                    |   Resolution:\n>  Keywords:                                            |\n> ------------------------------------------------------+---------------------\n\n\nComment (by Rajeev Thakur):\n\n {{{\n>\n>  Brian,\n>        I dug up your original bug report on the topic, and Ralph response\n>  to\n>  it is attached below. I guess the timeout value wasn't changed because the\n>  problem happens only on some machines and not msot others. In fact, we\n>  don't\n>  see it ourselves (otherwise we would have also complained).\n>\n>  In mpdman.py, you can change\n>       rv = self.streamHandler.handle_active_streams(timeout=5.0)\n>  to\n>       rv = self.streamHandler.handle_active_streams(timeout=0.2)\n>  in both source and installed versions.\n>\n>  Rajeev\n>\n>\n>  ----------------\n>  From: Ralph Butler <rbutler@mtsu.edu>\n>  Subject: Re: [MPICH2 Req #3190] Slight delay of mpiexec on process\n>  completion\n>  Date: Tue, 13 Feb 2007 10:17:22 -0600\n>  To: Brian Dushaw <dushaw@apl.washington.edu>\n>\n>  My guess is that all your investigations about redirection, stdin,\n>  sdout, etc. are a bit off the mark.  I would\n>  suspect that even this will typically hang at the end for 5 seconds:\n>       mpiexec -n 1 /bin/date\n>\n>  My students discovered over the weekend that this hanging phenomenon\n>  occurs on some of our\n>  machines.  It turns out that we can ONLY duplicate it on a box loaded\n>  with ubuntu linux.  We do NOT have\n>  the problem on debian, or MacOSX, or a couple of other flavors of\n>  unix laying around.  I believe that I have\n>  figured out how I want to fix the problem for the long-term and will\n>  apply it to cvs if it tests out OK.  In the\n>  meantime however, if you are looking for a quick-and-dirty fix, you\n>  could edit the mpdman.py file in\n>  your installed copy of mpd.  Change this:\n>       rv = self.streamHandler.handle_active_streams(timeout=5.0)\n>  to this:\n>       rv = self.streamHandler.handle_active_streams(timeout=0.2)\n>\n>  The 5.0 causes a 5 second delay, and we are reducing it to 0.2 (or\n>  some such small value).\n>\n>  If you do this, you need to stop and restart all running mpds.\n>\n>  > -----Original Message-----\n>  > From: mpich2-bugs-bounces@mcs.anl.gov\n>  > [mailto:mpich2-bugs-bounces@mcs.anl.gov] On Behalf Of mpich2\n>  > Sent: Wednesday, December 03, 2008 2:48 AM\n>  > To: undisclosed-recipients:\n>  > Subject: [mpich2-maint] #317: The infamous 5-s delay bug...\n>  >\n>  > ------------------------------------------------------+-------\n>  > --------------\n>  >  Reporter:  Brian Dushaw <dushaw@apl.washington.edu>  |\n>  >  Type:  bug\n>  >    Status:  new                                       |\n>  > Priority:  major\n>  > Milestone:                                            |\n>  > Component:  mpich2\n>  > ------------------------------------------------------+-------\n>  > --------------\n>  >\n>  >\n>  >  {{{\n>  >\n>  >  Dear MPICH-ers,\n>  >     I have compiled and installed the latest mpich - 1.0.8 - on my\n>  >  Suse linux 10.3 x64 system.  I am writing to report that a\n>  > bug (?) that\n>  >  we talked about some time ago still seems to exist.\n>  >     This is the annoying 5-s hang before an mpi job will finally\n>  >  complete.  All of the parallel jobs give their happy \"FORTRAN STOP\"s,\n>  >  but then mpich hangs for 5 s before finally completing.  It does not\n>  >  occur all the time, but often enough to be annoying.  I forget the\n>  >  details, other than perhaps that the issue seemed to occur only on\n>  >  specific systems.  The fix seems to be to edit one of the *.py\n>  >  scripts and change the \"timeout=5.0\" to \"timeout=0.1\", say.  I forget\n>  >  which script it is, alas.\n>  >     I am running my code with:\n>  >            time mpiexec -n 8 time ./mpiroutine < input.file\n>  >  if that makes a difference.\n>  >\n>  >     It has now been years and a few Suse upgrades since I\n>  > first reported\n>  >  the problem...ah hem.\n>  >     (Although the problem was occurring regularly a few minutes ago,\n>  >  it doesn't seem to be occurring now...seems to be one of THOSE kind\n>  >  of things...  Well, I'll report it.)\n>  >\n>  >  Thanks,\n>  >\n>  >  B.D.\n>  >\n>  >  %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%\n>  >\n>  >  Brian Dushaw\n>  >  Applied Physics Laboratory\n>  >  University of Washington\n>  >  1013 N.E. 40th Street\n>  >  Seattle, WA  98105-6698\n>  >  (206) 685-4198   (206) 543-1300\n>  >  (206) 543-6785 (fax)\n>  >  dushaw@apl.washington.edu\n>  >\n>  >  Web Page:  http://faculty.washington.edu/dushaw/index.html\n>  >  ```\n>  >\n>  >\n>  > --\n>  > Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/317>\n>  >\n>\n>  }}}\n\n--\nTicket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/317#comment:>\n}}}"}}
{"actor":{"display_login":"raffenet"}}