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

resharding/moveCollection/unshardCollection should not create indexes on shard not owning chunks

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 8.0.0
    • Component/s: None
    • Cluster Scalability
    • Cluster Scalability Priorities
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Today resharding/moveCollection/unshardCollection clones the indexes on the primary shard even if it's not the shard owning the collection, the indexes' definition will never get updated since the collection is resident on another shard.
      resharding/moveCollection/unshardCollection should not create any index on shards that are not owning the collection.

            Assignee:
            Unassigned Unassigned
            Reporter:
            renato.riccio@mongodb.com Renato Riccio
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None