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

For convertToCapped, router should not check if the collection is sharded itself

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Won't Fix
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Sharding
    • None
    • Sharding
    • ALL

    Description

      Currently the router checks its cache to see if the collection is sharded, and fails the convertToCapped operation if so. This is incorrect because the router's cache might be stale.

      Instead, the router should rely on the shard to check whether the collection is sharded.

      The router already attaches shardVersion, but the shard should actually check the shardVersion, which it does not currently do.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: