1. 10 Jan, 2012 1 commit
  2. 09 Jan, 2012 2 commits
  3. 06 Jan, 2012 1 commit
  4. 03 Jan, 2012 3 commits
  5. 20 Dec, 2011 1 commit
    • Vincent Pelletier's avatar
      Create masters as we are notified of their existence. · 59e7aafb
      Vincent Pelletier authored
      This increases cluster on-line flexibility, allowing new masters to be
      added without needing a restart of all masters.
      Downside is that more responsibility is pushed to cluster admins: they must
      update node configurations so they contain enough master nodes to allow
      them to join cluster after a restart.
      59e7aafb
  6. 09 Nov, 2011 1 commit
  7. 26 Oct, 2011 1 commit
  8. 05 Sep, 2011 1 commit
  9. 09 Jun, 2011 1 commit
  10. 02 May, 2011 1 commit
  11. 27 Apr, 2011 1 commit
    • Julien Muchembled's avatar
      connection: make close always call handler (connectionClosed or connectionFailed) · 4b6c1387
      Julien Muchembled authored
      Main reason is that it's difficult to know in advance which side really closes
      the connection. Network events can be chaotic and this could lead to many race
      conditions.
      Thus, handler can be used to update any database that is somewhat redundant
      to the connection status, i.e. node status usually. Safely and less duplicated
      code.
      
      This change is motivated by recurrent random failures during election.
      An example of race condition was that 2 fully connected master could close the
      extra connection (the primary -> secondary one) at the same time.
      
      In order to stabilize lower-level code and start with reliable election process,
      code has also been simplified to not care about node states. All connections
      without exception are closed at the end of the election and states are then
      updated 1 by 1 by identification handler.
      Note that during election, there may be 2 connection per node, which makes
      difficult to update node states by connectionFailed/connectionClosed events.
      
      timeoutExpired & peerBroken are dropped as they are unused for the moment.
      A new API should be designed so that connectionClosed know the reason of the
      close.
      BROKEN state becomes unused.
      
      git-svn-id: https://svn.erp5.org/repos/neo/trunk@2732 71dcc9de-d417-0410-9af5-da40c76e7ee4
      4b6c1387
  12. 07 Apr, 2011 2 commits
  13. 23 Mar, 2011 1 commit
  14. 21 Mar, 2011 1 commit
    • Julien Muchembled's avatar
      Small code cleanups · 75cd5ecb
      Julien Muchembled authored
      - remove useless calls to 'bool'
      - small optimizations in lib.protocol.Packet.__init__
      - code simplification in IdentificationHandler
      - fix typo in docstring
      - neo/tests/__init__.py: 2 lines were indented with 2-spaces instead of 4-spaces
      
      git-svn-id: https://svn.erp5.org/repos/neo/trunk@2671 71dcc9de-d417-0410-9af5-da40c76e7ee4
      75cd5ecb
  15. 25 Feb, 2011 1 commit
    • Olivier Cros's avatar
      Implementing ipv6 on neo · 0cdbf0ea
      Olivier Cros authored
      In order to synchronise neo with slapos, it has to work perfectly with ipv4
      and ipv6. This allows to integrate neo in erp5 and to prepare different buildout
      installations of neo.
      The protocol and connectors are no more generic but can now support IPv4 and
      IPv6 connections. We adopted a specific way of development which allow to
      easily add new protocols in the future.
      
      git-svn-id: https://svn.erp5.org/repos/neo/trunk@2654 71dcc9de-d417-0410-9af5-da40c76e7ee4
      0cdbf0ea
  16. 08 Feb, 2011 1 commit
  17. 17 Jan, 2011 1 commit
  18. 11 Jan, 2011 1 commit
    • Grégory Wisniewski's avatar
      Master transaction manager use TTID as index. · 2c3bea29
      Grégory Wisniewski authored
      - AnswerInformationLocked give ttid instead of tid
      - Master transaction manager always use ttid in data structures
      - It's no more makes sense to check if the tid is greater than the last
      generated as it never comes back from a storage, just check if the ttid is
      well known by the transaction manager.
      - Rename all tid variable that now hold a ttid
      - Transaction manager's queue contains ttids but the corresponding tids are
      increasing to keep commit order.
      - Adjust tests
      
      git-svn-id: https://svn.erp5.org/repos/neo/trunk@2613 71dcc9de-d417-0410-9af5-da40c76e7ee4
      2c3bea29
  19. 22 Dec, 2010 2 commits
  20. 14 Dec, 2010 1 commit
  21. 07 Dec, 2010 1 commit
  22. 08 Nov, 2010 1 commit
  23. 30 Oct, 2010 1 commit
  24. 29 Oct, 2010 2 commits
  25. 03 Sep, 2010 1 commit
  26. 21 Jun, 2010 2 commits
  27. 11 Jun, 2010 2 commits
  28. 07 Jun, 2010 1 commit
  29. 04 Jun, 2010 2 commits
  30. 24 May, 2010 2 commits