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

rollback does not correct sizeStorer data sizes

    XMLWordPrintableJSON

Details

    • Task
    • Status: Backlog
    • Major - P3
    • Resolution: Unresolved
    • None
    • None
    • Replication
    • Storage Execution
    • 18

    Description

      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.

      Attachments

        Issue Links

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-11113 Shard maxSize should be more accurate wrt space used/free

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-35565 Change capped collection age-out to be based on collection storageSize, not dataSize

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-34977 subtract capped deletes from fastcount during replication recovery

          • Major - P3 - Major loss of function.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. SERVER-31020 Sharding database creation is slow because of shard disk-usage statistics gathering

          • Major - P3 - Major loss of function.
          • Needs Scheduling

          Task - A task that needs to be done. DOCS-11792 Document that collection/database dataSize is no longer accurate in 4.0

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              backlog-server-execution Backlog - Storage Execution Team
              judah.schvimer@mongodb.com Judah Schvimer
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated: