Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-72875

Update architecture guide

    XMLWordPrintableJSON

Details

    • Icon: Improvement Improvement
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 7.0.0-rc0
    • None
    • None
    • None
    • Storage Execution
    • Fully Compatible
    • Execution Team 2023-02-20, Execution Team 2023-02-06, Execution Team 2023-03-06, Execution Team 2023-03-20, Execution Team 2023-04-03

    Description

      https://github.com/10gen/mongo/blob/d6b3993fcfc68d66fef6a25b268e0146e461857c/src/mongo/db/catalog/README.md?plain=1#LL1121C12-L1122

      The index logic is more relaxed because indexes do not go through two-phase drop when running with enableMajorityReadConcern=false

      https://github.com/10gen/mongo/blob/d6b3993fcfc68d66fef6a25b268e0146e461857c/src/mongo/db/catalog/README.md?plain=1#LL1321C54-L1323C7

      The Flow Control mechanism can be disabled
      explicitly via a server parameter and implicitly via setting enableMajorityReadConcern to
      false.

      Since 5.0 enableMajorityReadConcern is always true.

      Reconciling index builds: https://github.com/10gen/mongo/blob/d6b3993fcfc68d66fef6a25b268e0146e461857c/src/mongo/db/catalog/README.md?plain=1#L1124-L1134
      Refers to unfinished FCV 4.2- / FCV 4.4+ indexes.

      Empty sections:
      https://github.com/10gen/mongo/blob/d6b3993fcfc68d66fef6a25b268e0146e461857c/src/mongo/db/catalog/README.md?plain=1#L1151-L1153
      Recovery To A Stable Timestamp
      Table Ident Resolution

      Attachments

        Activity

          People

            daniel.gomezferro@mongodb.com Daniel Gomez Ferro
            daniel.gomezferro@mongodb.com Daniel Gomez Ferro
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: