Disallow single-phase foreground index builds on non-empty collections

ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • ALL
    • 200
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Single-phase foreground index builds have been used for internal collections, like config.shard.catalog.chunks in the past. The index build writes to the catalog after creating the new idents, with a timestamp gotten from a no-op oplog entry, but for rare cases of abort, the write to remove the index entry from the catalog is not timestamped. This write triggers the wt check to ensure no untimestamped writes after timestamped writes.

      We'd like to enforce that single-phase builds only happen on empty collections.

            Assignee:
            Unassigned
            Reporter:
            Yuhong Zhang
            Votes:
            1 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated: