1. 30 Mar, 2016 2 commits
  2. 28 Mar, 2016 2 commits
  3. 22 Mar, 2016 2 commits
  4. 21 Mar, 2016 3 commits
  5. 09 Mar, 2016 2 commits
  6. 08 Mar, 2016 2 commits
  7. 04 Mar, 2016 3 commits
  8. 02 Mar, 2016 1 commit
    • Julien Muchembled's avatar
      client: revert incorrect memory optimization · 763806e0
      Julien Muchembled authored
      Since commit d2d77437 ("client: make the cache
      tolerant to late invalidations when the entry is in the history queue"),
      invalidated items became current again when they were moved to the history
      queue, which was wrong for 2 reasons:
      - only the last items of _oid_dict values may have next_tid=None,
      - and for such items, they could be wrongly reused when caching the real
        current data.
      763806e0
  9. 01 Mar, 2016 1 commit
  10. 26 Feb, 2016 4 commits
  11. 05 Feb, 2016 1 commit
  12. 25 Jan, 2016 2 commits
  13. 21 Jan, 2016 2 commits
  14. 12 Jan, 2016 1 commit
  15. 16 Dec, 2015 2 commits
  16. 13 Dec, 2015 3 commits
  17. 12 Dec, 2015 1 commit
  18. 11 Dec, 2015 1 commit
  19. 09 Dec, 2015 1 commit
  20. 02 Dec, 2015 1 commit
  21. 01 Dec, 2015 3 commits
    • Julien Muchembled's avatar
    • Julien Muchembled's avatar
    • 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