Prevent resharding for unsharded capped collection from stashing collection

XMLWordPrintableJSON

    • Type: New Feature
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Cluster Scalability
    • 149
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      PM-3364 is enabling tracking of capped unsharded collection. Snapshot reads were unavailable for capped collections preventing resharding from running on capped collections (SERVER-86290 fixed it).

      The next error they are encountering is in the linked BF, it is an error for transactions on capped collections. Resharding stashes collection oplog entries from multiple donor nodes to ensure they are applied in order. The application happens inside the transaction. A capped unsplittable collection exists only on a single shard, so resharding can relax this restriction by not stashing the oplog entries for unsplittable/capped collection.

      Reproducer is attached to BF-32256

            Assignee:
            Cheahuychou Mao
            Reporter:
            Rachita Dhawan
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: