-
Type: Task
-
Resolution: Duplicate
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: Storage
-
Labels:None
-
Execution Team 2020-07-13, Execution Team 2020-07-27, Execution Team 2020-08-10
Rough starting outline:
The Catalog in-Memory Catalog Collection Catalog (include discussion of RecordStore interface) Index Catalog (include discussion of SortedDataInferface interface) Versioning (in memory versioning (or lack thereof) is separate from on disk) The Minimum Visible Snapshot On-Disk Catalog Catalog Data Formats Collection Data Format Index Data Format Versioning (e.g. data changes in tables are versioned, dropping/creating tables is not versioned) Catalog Changes (How are updates to the catalog done in-memory and on disk?) Two-Phase Collection and Index Drop (First phase removes access to the collection/index in the in-memory catalog, second phase drops the WT table.) (Explain this is necessary because WT versions document writes but not table drops.) (Necessary to support ongoing queries, repl ops like rollback, and our own startup recovery.)
Definitely feel free to alter the layout and file additional tickets split the work into more manageable units. Please add topics if you can think of any. This outline is meant only to be a starting point.
A couple helpful links for markdown basics:
https://www.markdowntutorial.com/
https://gist.github.com/asabaylus/3071099
https://markdownlivepreview.com/
- depends on
-
SERVER-47285 Execution Architecture Guide: The Catalog: In-Memory Catalog
- Closed
-
SERVER-47626 Execution Architecture Guide: The Catalog: On-Disk Catalog
- Closed
- duplicates
-
SERVER-47626 Execution Architecture Guide: The Catalog: On-Disk Catalog
- Closed
- is related to
-
SERVER-47628 Execution Architecture Guide: The Catalog: Two-Phase Collection and Index Drop
- Closed