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

fix collection counts in rollback without rebuilding indexes

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 4.1.7
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Fully Compatible
    • Storage NYC 2019-01-14

      Starting in SERVER-38769, rollback would not attempt to fix collection counts for drop-pending collections managed by the storage engine. This is because the drop-pending collection has been removed from the catalog while the underlying ident is kept around for rollback/recovery. The collection counts are eventually fixed coming out of rollback because rollback rebuilds the indexes on drop-pending collections in catalog::openCatalog().

      Once SERVER-38548 is completed, dropping indexes will defer the corresponding ident drops in a similar manner to what's currently done for collections. We should look into an alternate means of reconciling collection counts during rollback if we cannot rely on index rebuilds.

            Assignee:
            benety.goh@mongodb.com Benety Goh
            Reporter:
            benety.goh@mongodb.com Benety Goh
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: