Skip to content
Snippets Groups Projects
  1. Aug 15, 2017
  2. Aug 14, 2017
  3. Aug 11, 2017
  4. Aug 10, 2017
  5. Aug 08, 2017
  6. Aug 07, 2017
  7. Aug 04, 2017
  8. Aug 02, 2017
  9. Aug 01, 2017
  10. Jul 31, 2017
  11. Jul 28, 2017
  12. Jul 27, 2017
    • Alejandro Sanchez's avatar
      Fix bug when tracking multiple simultaneous spawned ping cycles · f7463ef5
      Alejandro Sanchez authored
      When more than 1 ping cycle is spawned simultaneously (for instance
      REQUEST_PING + REQUEST_NODE_REGISTRATION_STATUS for the selected nodes),
      we do not track a separate ping_start time for each cycle. When ping_begin()
      is called, the information about the previous ping cycle is lost. Then when
      ping_end() is called for the first of the two cycles, we set ping_start=0,
      which is incorrectly used to see if the last cycle ran for more than
      PING_TIMEOUT seconds (100s), thus incorrectly triggering the:
      
       error("Node ping apparently hung, many nodes may be DOWN or configured "
             "SlurmdTimeout should be increased");
      
      Bug 3914
      f7463ef5
    • Tim Shaw's avatar
      04b431b4
Loading