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

Convert tassert in CheckMetadataConsistency into a proper inconsistency

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Sharding EMEA 2023-05-01, Sharding EMEA 2023-05-15

      Originally we added this tassert that is triggered when a shard has a collection marked as UNSHARDED in its CollectionShardingState while instead is actually sharded.

      We discovered that due to the bug described in SERVER-76489, this can actually happen, and it will bring to data-loss scenarios. Thus, I believe that we should report this as an inconsistency rather than failing the entire CheckMetadataConsistency command.

            Assignee:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Reporter:
            tommaso.tocci@mongodb.com Tommaso Tocci
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: