1. 30 Nov, 2015 1 commit
    • Minimize the amount of work during tpc_finish · 7eb7cf1b
      NEO did not ensure that all data and metadata are written on disk before
      tpc_finish, and it was for example vulnerable to ENOSPC errors.
      In other words, some work had to be moved to tpc_vote:
      
      - In tpc_vote, all involved storage nodes are now asked to write all metadata
        to ttrans/tobj and _commit_. Because the final tid is not known yet, the tid
        column of ttrans and tobj now contains NULL and the ttid respectively.
      
      - In tpc_finish, AskLockInformation is still required for read locking,
        ttrans.tid is updated with the final value and this change is _committed_.
      
      - The verification phase is greatly simplified, more reliable and faster. For
        all voted transactions, we can know if a tpc_finish was started by getting
        the final tid from the ttid, either from ttrans or from trans. And we know
        that such transactions can't be partial so we don't need to check oids.
      
      So in addition to minimizing the risk of failures during tpc_finish, we also
      fix a bug causing the verification phase to discard transactions with objects
      for which readCurrent was called.
      
      On performance side:
      
      - Although tpc_vote now asks all involved storages, instead of only those
        storing the transaction metadata, the client has been improved to do this
        in parallel. The additional commits are also all done in parallel.
      
      - A possible improvement to compensate the additional commits is to delay the
        commit done by the unlock.
      
      - By minimizing the time to lock transactions, objects are read-locked for a
        much shorter period. This is even more important that locked transactions
        must be unlocked in the same order.
      
      Transactions with too many modified objects will now timeout inside tpc_vote
      instead of tpc_finish. Of course, such transactions may still cause other
      transaction to timeout in tpc_finish.
      Julien Muchembled committed
  2. 21 Oct, 2015 1 commit
    • Do not send invalidations for objects on which only readCurrent was called · 9682722b
      This fixes invalid next_serial entries in cache,
      and the following error for values not in cache:
      
        Traceback (most recent call last):
          File "ZODB/Connection.py", line 856, in setstate
            self._setstate(obj)
          File "ZODB/Connection.py", line 894, in _setstate
            self._load_before_or_conflict(obj)
          File "ZODB/Connection.py", line 922, in _load_before_or_conflict
            if not self._setstate_noncurrent(obj):
          File "ZODB/Connection.py", line 945, in _setstate_noncurrent
            assert end is not None
        AssertionError
      Julien Muchembled committed
  3. 21 May, 2015 1 commit
  4. 03 Jun, 2014 1 commit
  5. 07 Jan, 2014 1 commit
  6. 17 Dec, 2013 2 commits
  7. 20 Aug, 2012 2 commits
  8. 26 Jul, 2012 1 commit
  9. 13 Mar, 2012 1 commit
  10. 26 Oct, 2011 1 commit
  11. 05 Sep, 2011 1 commit
  12. 07 Apr, 2011 1 commit
  13. 08 Feb, 2011 1 commit
  14. 17 Jan, 2011 1 commit
  15. 22 Dec, 2010 1 commit
  16. 14 Dec, 2010 3 commits
  17. 07 Dec, 2010 2 commits
  18. 29 Oct, 2010 2 commits
  19. 03 Sep, 2010 1 commit
  20. 27 Aug, 2010 2 commits
  21. 21 Jun, 2010 1 commit
  22. 17 Jun, 2010 1 commit
  23. 04 Jun, 2010 2 commits
  24. 13 May, 2010 3 commits
  25. 22 Feb, 2010 1 commit
  26. 08 Feb, 2010 1 commit
  27. 03 Feb, 2010 1 commit
  28. 01 Feb, 2010 2 commits
  29. 26 Jan, 2010 1 commit