svn commit: r1779903 - in /jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment: changes.md overview.md

[fr...@apache.org]

Author: frm
Date: Mon Jan 23 11:03:11 2017
New Revision: 1779903

URL: http://svn.apache.org/viewvc?rev=1779903&view=rev
Log:
OAK-4833 - Document changes in the data format

Added:
    jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment/changes.md
Modified:
    jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment/overview.md

Added: jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment/changes.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment/changes.md?rev=1779903&view=auto
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment/changes.md (added)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment/changes.md Mon Jan 23 11:03:11 2017
@@ -0,0 +1,164 @@
+<!--
+  Licensed to the Apache Software Foundation (ASF) under one or more
+  contributor license agreements.  See the NOTICE file distributed with
+  this work for additional information regarding copyright ownership.
+  The ASF licenses this file to You under the Apache License, Version 2.0
+  (the "License"); you may not use this file except in compliance with
+  the License.  You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+  Unless required by applicable law or agreed to in writing, software
+  distributed under the License is distributed on an "AS IS" BASIS,
+  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+  See the License for the specific language governing permissions and
+  limitations under the License.
+-->
+
+# Changes in the data format
+
+This document describes the changes in the data format introduced by the Oak Segment Tar module.
+The purpose of this document is not only to enumerate such changes, but also to explain the rationale behind them.
+Pointers to Jira issues are provided for a much more terse description of changes.
+Changes are presented in chronological order.
+
+## Generation in segment headers
+
+* Jira issue: [OAK-3348](https://issues.apache.org/jira/browse/OAK-3348)
+* Since: Oak Segment Tar 0.0.2
+
+The GC algorithm implemented by Oak Segment Tar is based on the fundamental idea of grouping records into generations.
+When GC is performed, records belonging to older generations can be removed, while records belonging to newer generations have to be retained.
+
+The fact that a record belongs to a generation is not a transient piece of information: it has to survive across multiple restarts of the system.
+This means that the generation of a record has to be persisted together with the record.
+
+To not incur in the size penalty of persisting additional information for each and every record, the generation is persisted only once in the segment header.
+Thus, the generation of a record is defined as the generation of the segment containing that record.
+
+The original data format for the segment header contained some holes in the specification.
+The change made good use of one of those holes (bytes 10-13) to save the generation as a 4-byte integer value.
+
+## Stable identifiers 
+
+* Jira issue: [OAK-3348](https://issues.apache.org/jira/browse/OAK-3348)
+* Since: Oak Segment Tar 0.0.2
+
+The fastest way to compare two node records is to compare their addresses.
+If their addresses are equal, the two node records are guaranteed to be equal.
+Transitively, given that records are immutable, the subtrees identified by those node records are guaranteed to be equal.
+
+The situation gets more complicated when the generation-based GC algorithm copies a node record over a new generation to save it from being deleted.
+In this situation, two copies of the same node record live in two different generations, in two different segments and at two different addresses.
+If you want to figure out if those two node records are the same, the trick of comparing their addresses will not work anymore.
+
+To overcome this problem, a stable identifier has been added to every node record.
+When a new node record is serialized, the address it is serialized to becomes its stable identifier.
+The stable identifier is included in the node record and becomes part of its serialized format.
+
+When the node record is copied to a new generation and a new segment, its address will inevitably change.
+The stable identifier instead, being part of the node record itself, will not change.
+This enables fast comparison between different copies of the same node records.
+Instead of comparing their addresses, you can compare their stable identifiers to achieve the same result.
+
+The stable identifier is serialized as a 18-bytes-long string record.
+This record, in turn, is referenced from the node record by adding an additional 3-bytes-long reference field to it.
+In conclusion, stable identifiers add an overhead of 21 bytes to every node record in the worst case.
+In the best case, the 18-bytes-long string record is shared between node records when possible, so the aforementioned overhead represents an upper limit.
+
+## Binary references index
+
+* Jira issue: [OAK-4201](https://issues.apache.org/jira/browse/OAK-4201)
+* Since: Oak Segment Tar 0.0.4
+
+The original data format in Oak Segment mandates that every segment maintains a list of references to external binaries.
+Every time a record references an external binary - i.e. a piece of binary data that is stored in a Blob Store - a new binary reference is added to its segment.
+The list of references to external binaries is inspected periodically by the Blob Store GC algorithm to know which binaries are currently in use.
+The Blob Store GC algorithm removes every binary that is not reported as used by the Segment Store.
+
+Retrieving the comprehensive list of external binaries for the whole repository is an expensive operation when it comes to I/O.
+In the worst case, every segment in every TAR file has to be read in memory and the list of references to external binaries have to be parsed.
+Even if a segment does not contain references to external binaries, it has to be read in memory first for the system to figure it out.
+
+To make this process faster and less greedy for I/O resources, Oak Segment Tar introduces an index of references to external binaries in every TAR file.
+This index aggregates the required information from every segment contained in a TAR file.
+When Blob Store GC is performed, instead of reading and parsing every segment, you can read and parse the index files.
+This optimization may reduce the amount of I/O operations of an order of magnitude in the best case.
+
+## Simplified segment and record format
+
+* Jira issue: [OAK-4631](https://issues.apache.org/jira/browse/OAK-4631)
+* Since: Oak Segment Tar 0.0.10
+
+The old data format specified Oak Segment has a strong limit on the number of references to other segments that could be stored in the segment header.
+This limitation caused sub-optimal segment space utilization when a record referencing data from a large amount of different segments was written.
+This kind of records quickly exhausted the hard limit on the number of references to other segments, causing a premature flush of a half-full segment.
+
+Oak Segment Tar relaxed the hard limit on the number of segments to the point that it can now be considered irrelevant.
+This change avoids the obvious problem of segment space utilization.
+Tests show that with this change in place it is possible to store the same amount of data in a smaller amount of better utilized segments.
+
+The Jira issue referenced in this paragraph proposes other changes other than the one discussed here.
+Most of the changes proposed by the issue were subsequently reverted or never made in the code base because of their high toll on disk space.
+Reading the issue and the referenced email thread can anyway be a good exercise if you feel inspired.
+
+## Storage format versioning
+
+* Jira issue: [OAK-4295](https://issues.apache.org/jira/browse/OAK-4295)
+* Since: Oak Segment Tar 0.0.10
+
+To avoid the old Oak Segment and the new Oak Segment Tar to step on each other's toes, an improved versioning mechanism of the data format was introduced.
+   
+First of all, the version field in the segment header in Oak Segment Tar has been incremented.
+This prevents Oak Segment Tar from reading and parsing segments written by the old implementation and Oak Segment from doing the same with newer segments.
+
+This strategy has been further improved by adding a manifest file in every data folder created by Oak Segment Tar.
+The manifest file is supposed to be a source of metadata for the whole repository.
+Oak Segment Tar checks for the presence of a manifest file very time a data folder is open.
+If a manifest file is there, the metadata has to be compatible with the current version of the currently executing code.
+
+Repositories written by the old Oak Segment don't generate a manifest file.
+This difference between the two implementations enables a fail-fast approach.
+When Oak Segment opens a data folder containing a manifest, it immediately fails complaining that the data format is too new.
+When Oak Segment opens a non-empty data folder without a manifest, it immediately fails complaining that the data format is too old.
+
+## Logic record IDs
+
+* Jira issue: [OAK-4659](https://issues.apache.org/jira/browse/OAK-4659)
+* Since: Oak Segment Tar 0.0.14
+
+The old implementation in Oak Segment considers the position of every record immutable.
+Once written, the coordinates to locate a record in the segment store is the ID of a segment and the offset of the record in the segment.
+The offset is the effective position of the record in the segment.
+
+This way of addressing record implies that records can't be moved around.
+Moving a record means changing its segment, its position or both.
+Moving a record is a destructive operation: every reference to that record is effectively broken.
+
+To gain more flexibility in storing records, a new level of indirection was introduced with logic record IDs.
+Instead of referencing a record by a segment ID and the position of the record in that segment, a segment ID and a record number is used.
+The record number is a logic address for a record in the segment and is local to the segment.
+
+With this solution the record can be moved within the segment without changing the way it is referenced.
+This change enables a number of different algorithms when it comes to garbage collection.
+In example, some records can now be removed from a segment and the segment can be shrunk down by moving every remaining record next to each other.
+This operation would change the position of the remaining record in the segment, but not their logic record ID.
+
+The change introduced a new translation table in the segment header to map record numbers to record offsets.
+The table occupies 9 bytes per record (4 bytes for the record number, 1 byte for the record type and 4 bytes for the record offset).
+Moreover, a new 4-bytes-long integer field has been added to the segment header containing the number of entries of the translation table.
+
+## Root record types
+
+* Jira issue: [OAK-2498](https://issues.apache.org/jira/browse/OAK-2498)
+* Since: Oak Segment Tar 0.0.16
+
+The record number translation table mentioned in the previous paragraph contains a 1-byte field for every record.
+This field determines the type of the record referenced by that line of the table.
+The change in this paragraph is about improving the information stored in the type field of the record number translation table.
+
+The bulk of this change is the introduction of a new record type identifying records pointing to external binary data, e.g. data contained in an external Blob Store.
+This is a very important information to have at hand, because it allows Oak Segment Tar to efficiently reconstruct or populate the index of binary references.
+Being able to cheaply identify references to external binaries is of paramount importance when a recovery operation is performed after a crash or a data corruption.
+The recovery algorithm doesn't have access to the whole repository, but needs to work on a segment at a time.
+The additional record type allows the recovery algorithm to correctly recover the index of binary references even if only the segment at hand is considered without further context.
\ No newline at end of file

Modified: jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment/overview.md
URL: http://svn.apache.org/viewvc/jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment/overview.md?rev=1779903&r1=1779902&r2=1779903&view=diff
==============================================================================
--- jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment/overview.md (original)
+++ jackrabbit/oak/trunk/oak-doc/src/site/markdown/nodestore/segment/overview.md Mon Jan 23 11:03:11 2017
@@ -50,6 +50,7 @@ Oak Segment Tar is an implementation of
     * [Diff](#diff)
     * [History](#history)
 * [Design](#design)
+    * [Format changes](#format-changes)
 
 ## <a name="garbage-collection"/> Garbage Collection
 
@@ -642,3 +643,9 @@ You can learn about the internal organiz
 
 This website also contains an overview of the legacy implementation of the Segment Store and of the design decisions that brought to this implementation.
 The page is old and describes a deprecated implementation, but can still be accessed [here](../segmentmk.html).
+
+### <a name="format-changes"/> Format changes
+
+The Oak Segment Tar module introduces a number of changes in the data format compared to the legacy Oak Segment.
+The changes are described in greater detail [here](changes.html).
+Pointers to actual Jira issues can also be found on that page.