An error occurred fetching the project authors.
  1. 24 Feb, 2005 1 commit
  2. 23 Feb, 2005 1 commit
  3. 17 Feb, 2005 2 commits
  4. 16 Feb, 2005 1 commit
  5. 11 Feb, 2005 1 commit
  6. 09 Feb, 2005 1 commit
    • stewart@mysql.com's avatar
      Impl5 of WL2278 - dynamic port allocation for cluster nodes · e795feca
      stewart@mysql.com authored
      Treat the management server specially.
      
      It should always be the server in a transporter as we then have a known
      port to connect to on node restart.
      
      allows a mgm connection (i.e. to the management server port, our known port)
      to be transformed into a transporter connection.
      
      Also, clean up the struct TransporterConfiguration (used to be a struct for
      each transporter type. now there's just one)
      e795feca
  7. 14 Jan, 2005 1 commit
  8. 12 Jan, 2005 1 commit
    • stewart@mysql.com's avatar
      Impl4 of WL2278 - Dynamic port allocation of cluster nodes · ac28b470
      stewart@mysql.com authored
      When a node restarts it starts over again with fetching the configuration
      -  It is not sure that it can use the "old dynamically allocated port number" again.
      -  It should however try to reuse the old one, if not possible it should
      allocate a new one. One has to be able to distinguish between portnumbers
      specified originally in the config, and ones that has been dynamically added
      (the latter may be changed if "busy", but the first cannot be changed).
      
      We use negative portnumbers for ports that are ok to change.
      ac28b470
  9. 23 Dec, 2004 1 commit
  10. 22 Dec, 2004 1 commit
  11. 16 Dec, 2004 1 commit
  12. 14 Dec, 2004 2 commits
  13. 09 Nov, 2004 1 commit
  14. 16 Sep, 2004 1 commit
  15. 24 Jun, 2004 1 commit
  16. 23 Jun, 2004 1 commit
  17. 14 Apr, 2004 1 commit