'Lock tree manager' object created to hold data shared by all lock trees
i.e. Current number of locks (per env) and max locks (per env)
Uses functions to change max_locks.
Added tests for lock tree manager.


git-svn-id: file:///svn/tokudb@2948 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2946 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2945 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2944 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2943 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2942 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2941 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2940 c7de825b-a66e-492c-adef-691d508d4ae1

Create test_log6a_abort.c.   Returns {{{ENOMEM}}} from {{{r = toku_lt_acquire_write_lock(db->i->lt, toku_txn_ancestor(txn...)...)}}} in ydb.c:2126.  Addresss #536.  Maybe also Addresses #501. (?).

git-svn-id: file:///svn/tokudb@2932 c7de825b-a66e-492c-adef-691d508d4ae1

create iterator for lth

git-svn-id: file:///svn/tokudb@2930 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2929 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2925 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2923 c7de825b-a66e-492c-adef-691d508d4ae1

always have lock escalation to be turned on

git-svn-id: file:///svn/tokudb@2919 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2918 c7de825b-a66e-492c-adef-691d508d4ae1

The final fix for this bug involves writing zeros into the unused bytes of the disk when serializing nodes.  
This is important for two reasons:
 1. It makes the files the same the bit-level.  (The problem showed up because a node of size near 1MB was written, and then the node split, causing the node to shrink, and when the node was written again, some left over bits from the previous node were still on disk.  Then the file compare failed after recovery.)
 1. It causes the file system to actually allocate the space for a node, so that when a node grows, it will all be contiguous on disk.

It has the disadvantage of writing more to disk than we did before, possibly reducing performance.  It probably doesn't matter much, however. 


git-svn-id: file:///svn/tokudb@2916 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2914 c7de825b-a66e-492c-adef-691d508d4ae1

Fixes many problems in {{{test_log10}}}.  There's a memory leak and the recovered files still differ, however.  Addresses #548.

git-svn-id: file:///svn/tokudb@2913 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2912 c7de825b-a66e-492c-adef-691d508d4ae1

Fixes a bug with escalation caught by valgrind.


git-svn-id: file:///svn/tokudb@2904 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2903 c7de825b-a66e-492c-adef-691d508d4ae1

implemented lock escalation MINUS flagging of messy transactions
implemented tests for lock escalation

git-svn-id: file:///svn/tokudb@2902 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2900 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2898 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2895 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2893 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2892 c7de825b-a66e-492c-adef-691d508d4ae1

test_thread_insert doesn't leak memory any more.  The leak is in {{{pthread_exit()}}}.  If you return from the initial function, the leak isn't there.  Fixes #303.

git-svn-id: file:///svn/tokudb@2884 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2883 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2882 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2881 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2880 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2877 c7de825b-a66e-492c-adef-691d508d4ae1

Reordered escalation.
First escalate writes, and only if that succeeds, we escalate the reads.
Now, if we fail during the reads we are still consistent, whereas before
we would need to panic.

git-svn-id: file:///svn/tokudb@2876 c7de825b-a66e-492c-adef-691d508d4ae1

Implemented testing if escalating a range from borderwrite is trivial.

git-svn-id: file:///svn/tokudb@2875 c7de825b-a66e-492c-adef-691d508d4ae1

Started coding lock escalation.
Have several function stubs that need to be implemented.

git-svn-id: file:///svn/tokudb@2874 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2873 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2871 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2870 c7de825b-a66e-492c-adef-691d508d4ae1

git-svn-id: file:///svn/tokudb@2869 c7de825b-a66e-492c-adef-691d508d4ae1