An error occurred fetching the project authors.
  1. 13 Oct, 2005 1 commit
  2. 03 Oct, 2005 1 commit
  3. 30 Sep, 2005 1 commit
  4. 22 Sep, 2005 1 commit
  5. 21 Sep, 2005 1 commit
  6. 20 Sep, 2005 1 commit
  7. 12 Sep, 2005 4 commits
  8. 08 Sep, 2005 3 commits
  9. 05 Sep, 2005 1 commit
  10. 18 Aug, 2005 1 commit
  11. 15 Jul, 2005 1 commit
  12. 14 Jul, 2005 1 commit
    • tomas@poseidon.ndb.mysql.com's avatar
      misc (memleak) fixes: · ec52d680
      tomas@poseidon.ndb.mysql.com authored
          added using ndb_end and showing mem allocation stat at exit
          added init of variable
          added destruction of LocalConfig to still memleak
          added delete of theFacade on exit
          stopSessions(true) on socket server to ensure destuction of threads
          added destruction of arbit manager thread
          added true option to stopSessions in transporter facade to ensure destructions of threads
      ec52d680
  13. 22 Apr, 2005 1 commit
  14. 12 Apr, 2005 2 commits
  15. 04 Mar, 2005 2 commits
  16. 21 Feb, 2005 1 commit
  17. 16 Feb, 2005 1 commit
  18. 15 Feb, 2005 1 commit
  19. 14 Feb, 2005 3 commits
  20. 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
  21. 01 Feb, 2005 1 commit
  22. 19 Jan, 2005 1 commit
  23. 14 Jan, 2005 1 commit
  24. 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
  25. 11 Jan, 2005 1 commit
  26. 07 Jan, 2005 1 commit
  27. 04 Jan, 2005 1 commit
  28. 23 Dec, 2004 1 commit
  29. 22 Dec, 2004 1 commit
  30. 20 Dec, 2004 2 commits
    • tomas@poseidon.ndb.mysql.com's avatar
      added config parameter Group on connection · 7b47be89
      tomas@poseidon.ndb.mysql.com authored
          moved NdbWaiter, m_ndb_cluster_connection, to impl class
          moved node selection things to cluster connection
          moved all private things to impl class
          added opts for shared memory and node selection
          changed opts handling somewhat; introduced enum for options and common handling of option variables
          added checks for transporter support
          automatic addition of shared mem transporters
          moved wait_until_ready code to cluster connection
          added control of usage of new node selection method
      7b47be89
    • stewart@mysql.com's avatar
      Part 1 of impl2 of WL2278 (Dynamic port allocation of cluster nodes). · 4382caa0
      stewart@mysql.com authored
      Implementation of "get connection parameter" mgmd call for getting from mgmd what port to use for a connection between two nodes.
      
      (The actual use of this function is not yet implemented)
      4382caa0