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

shard should clear its own CollectionShardingState on dropCollection

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Works as Designed
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: 3.7.7
    • Component/s: Sharding
    • Labels:
      None
    • Sharding
    • ALL

      This would eliminate a class of bugs (some which show up in BF's) where the setShardVersion for dropCollection is not sent due to a config failover.

            Assignee:
            backlog-server-sharding [DO NOT USE] Backlog - Sharding Team
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: