1. 27 Apr, 2019 2 commits
  2. 11 Mar, 2019 1 commit
  3. 18 Jan, 2017 1 commit
  4. 25 Jan, 2016 1 commit
  5. 01 Dec, 2015 1 commit
    • Julien Muchembled's avatar
      Safer DB truncation, new 'truncate' ctl command · d3c8b76d
      Julien Muchembled authored
      With the previous commit, the request to truncate the DB was not stored
      persistently, which means that this operation was still vulnerable to the case
      where the master is restarted after some nodes, but not all, have already
      truncated. The master didn't have the information to fix this and the result
      was a DB partially truncated.
      
      -> On a Truncate packet, a storage node only stores the tid somewhere, to send
         it back to the master, which stays in RECOVERING state as long as any node
         has a different value than that of the node with the latest partition table.
      
      We also want to make sure that there is no unfinished data, because a user may
      truncate at a tid higher than a locked one.
      
      -> Truncation is now effective at the end on the VERIFYING phase, just before
         returning the last ids to the master.
      
      At last all nodes should be truncated, to avoid that an offline node comes back
      with a different history. Currently, this would not be an issue since
      replication is always restart from the beginning, but later we'd like they
      remember where they stopped to replicate.
      
      -> If a truncation is requested, the master waits for all nodes to be pending,
         even if it was previously started (the user can still force the cluster to
         start with neoctl). And any lost node during verification also causes the
         master to go back to recovery.
      
      Obviously, the protocol has been changed to split the LastIDs packet and
      introduce a new Recovery, since it does not make sense anymore to ask last ids
      during recovery.
      d3c8b76d
  6. 21 May, 2015 1 commit
  7. 07 Jan, 2014 1 commit
  8. 20 Aug, 2012 1 commit
  9. 13 Mar, 2012 1 commit
  10. 28 Feb, 2012 1 commit
  11. 05 Jan, 2012 1 commit
  12. 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
  13. 17 Jan, 2011 1 commit
  14. 05 Nov, 2010 1 commit
  15. 01 Feb, 2010 2 commits
  16. 28 Jan, 2010 1 commit
  17. 07 Oct, 2009 1 commit
  18. 05 Oct, 2009 1 commit
  19. 01 Oct, 2009 3 commits
  20. 03 Aug, 2009 2 commits
  21. 28 Jul, 2009 1 commit
  22. 27 Jul, 2009 1 commit
  23. 22 Jul, 2009 1 commit
  24. 21 Jul, 2009 1 commit
  25. 20 Jul, 2009 1 commit
  26. 08 Jul, 2009 1 commit
  27. 03 Jul, 2009 1 commit
  28. 29 Jun, 2009 1 commit
  29. 26 Jun, 2009 1 commit
  30. 24 Jun, 2009 1 commit
  31. 23 Jun, 2009 1 commit
  32. 22 Jun, 2009 1 commit
  33. 27 May, 2009 1 commit
  34. 25 May, 2009 1 commit