• unknown's avatar
    BUG#11132 Connections stuck in CLOSE_WAIT · a8e426d2
    unknown authored
    This fixes the problem in 5.0 in the correct way.
    
    The previous patch (for 4.1) is only valid for 4.1 and is done at the right time
    for 4.1.
    
    
    ndb/src/kernel/main.cpp:
      The ndbd angel process keeps the mgm connection open as it retains a reference
      to the socket.
      
      this means that when the mgm server is killed, the socket stays in CLOSE_WAIT 
      (the ndb process will close() it okay in 5.0, as we reused it for a transporter
      but this isn't enough as the angel process still has a reference to that socket).
      
      so, by adding in a theConfig->closeConfiguration(); in the angel process, the ndb
      process is left with the only reference to the socket - which it can close whenever
      it likes (namely when the connection is terminated).
    a8e426d2
main.cpp 9.78 KB