Disallow existing config.image_collection entry to go from invalid to valid

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Replication
    • Sharding NYC 2023-09-18, Sharding NYC 2023-10-02, Sharding NYC 2023-10-16, Sharding NYC 2023-10-30, Cluster Scalability 2023-11-13, Cluster Scalability 2023-11-27, Cluster Scalability 2023-12-11, Cluster Scalability 2023-12-25, Cluster Scalability 2024-1-8, Cluster Scalability 2024-1-22, Cluster Scalability 2024-2-5, Cluster Scalability 2024-2-19, Cluster Scalability 2024-3-4, Cluster Scalability 2024-3-18, Cluster Scalability 2024-4-1, Cluster Scalability 2024-4-15
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-68209 makes it legal to overwrite an existing config.image_collection entry with lsid, txnNumber and ts by removing this uassert. We should repurpose to removed uassert to fail if the incoming entry doesn't have "invalidated" set to true. This case should never get hit since it shouldn't be possible for an entry to go from invalid to valid.

            Assignee:
            Unassigned
            Reporter:
            Cheahuychou Mao
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: