Merge lp:~akiban-technologies/akiban-persistit/releases_notes_3.1.2 into lp:akiban-persistit

Proposed by Peter Beaman
Status: Merged
Approved by: Nathan Williams
Approved revision: 332
Merged at revision: 332
Proposed branch: lp:~akiban-technologies/akiban-persistit/releases_notes_3.1.2
Merge into: lp:akiban-persistit
Diff against target: 45 lines (+26/-2)
1 file modified
doc/ReleaseNotes.rst (+26/-2)
To merge this branch: bzr merge lp:~akiban-technologies/akiban-persistit/releases_notes_3.1.2
Reviewer Review Type Date Requested Status
Nathan Williams Approve
Review via email: mp+114734@code.launchpad.net

Description of the change

Small additions to the 3.1.2 Release Notes version started by Nathan.

LBJ: NO_BUILD

To post a comment you must log in.
Revision history for this message
Nathan Williams (nwilliams) wrote :

Looks good.

I also forgot to let the team know about the new trick, but adding LBJ: NO_BUILD to the end of the description will skip the full build process. I've modified it as such.

review: Approve

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'doc/ReleaseNotes.rst'
2--- doc/ReleaseNotes.rst 2012-06-15 17:28:09 +0000
3+++ doc/ReleaseNotes.rst 2012-07-12 21:08:22 +0000
4@@ -50,7 +50,7 @@
5
6 Release Date
7 ============
8-June 15, 2012
9+July 13, 2012
10
11 Overview
12 ========
13@@ -81,7 +81,31 @@
14
15 https://bugs.launchpad.net/bugs/1012859
16
17-This bug preexisted, but was unknown to, the 3.1.1 release. If a thread starting a new transaction was interrupted during the call to ``begin()``, there was a chance for an internal object to wind up in an invalid state. This invalid state caused no visible consequences other than slower than expected ``Accumulator`` actions if this had occurred many times.
18+This bug preexisted but was unknown to the 3.1.1 release. If a thread starting a new transaction was interrupted during the call to ``begin()``, there was a chance for an internal object to wind up in an invalid state. This invalid state caused no visible consequences other than slower than expected ``Accumulator`` actions if this had occurred many times.
19+
20+B+Tree Corruption in Stress Test
21+--------------------------------
22+
23+https://bugs.launchpad.net/akiban-persistit/+bug/1017957
24+
25+This bug preexisted but was unknown to the 3.1.1 release. An extremely rare combination of events caused memory structures caused an incorrect key-pointer pair to be inserted while deleting records in a key range. The bug was detected in an 8-hour stress test run.
26+
27+
28+Slow Recovery Due to Temporary Tree IT Records
29+----------------------------------------------
30+
31+https://bugs.launchpad.net/akiban-persistit/+bug/1018526
32+
33+This bug preexisted but was unknown to the 3.1.1 release.
34+
35+Every Tree created in a temporary volume was being assigned a tree handle recorded permanently in the journal. In one case the result was a journal containing millions of IT (Identify Tree) records, and these caused normal recovery to take a very long time. The fix keeps temporary trees out of the journal and removes IT records which may have been added previously.
36+
37+
38+Asserts Added to Check for Correct Exchange Thread Behavior
39+-----------------------------------------------------------
40+
41+A bug in the Akiban Server code caused a an Exchange to be used concurrently by two Threads, causing serious and seemingly unrelated failures in Persistit including instances of IllegalMonitorException and IllegalStateException. To guard against future occurrences, asserts were added to catch such concurrent use by multiple threads. Applications should be tested with asserts enabled to verify correct thread usage.
42+
43
44 Known Issues
45 ============

Subscribers

People subscribed via source and target branches

to all changes: