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

rollback does not correct sizeStorer data sizes

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Replication
    • Labels:
    • Storage Execution
    • 18

      We just keep the data size the same when we recover to a stable timestamp instead of correcting it like we do with counts: https://github.com/mongodb/mongo/blob/f757bc52b926943bc748f0dc33173ab16e980f61/src/mongo/db/repl/storage_interface_impl.cpp#L1025-L1028

      This means that the size reported in collStats will be wrong, it also can have the side effect of slowly decreasing the effective size of a capped collection, since the system will think it's more full than it actually is. Validate will fix the size.

            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            judah.schvimer@mongodb.com Judah Schvimer
            0 Vote for this issue
            13 Start watching this issue