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

Ensure capped:true and recordIdsReplicated:true interact correctly

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Execution
    • Execution Team 2024-05-13

      Capped collections seem to reserve their recordIds separately. Currently we're following the model of making sure that a collection can't be both capped:true and recordIdsReplicated:true. But it might be worth changing this to allow capped collections to have recordIdsReplicated:true.

      Also to be considered while doing this is how the cloneCollectionAsCapped and convertToCapped commands should behave. We need to make sure that they are correct.

      In particular, during initial sync the node seems to crash on capped_converToCapped1.js because a collection with recordIdsReplicated:true ends up being converted and then obtains the capped:true property as well. See comments.

            Assignee:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Reporter:
            vishnu.kaushik@mongodb.com Vishnu Kaushik
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: