Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-15590

[Server] Warn users that they cannot change index type when running refineshardkey

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Critical - P2
    • Resolution: Done
    • None
    • 4.4.0, 5.0.0, 6.0.0
    • manual, Server
    • None

    Description

      We should update

      https://www.mongodb.com/docs/manual/core/sharding-refine-a-shard-key/

      and

      https://www.mongodb.com/docs/manual/reference/command/refineCollectionShardKey/#mongodb-dbcommand-dbcmd.refineCollectionShardKey

      to more explicitly state that you cannot modify the index type as part of this operation. In some versions this will succeed (SERVER-69220 will block it), but introduce sharding metadata inconsistencies.

      For example, users should not refine from {a:1} to {a:"hashed",b:1}. As this would make the routing table not match the physical location of the documents.

      Attachments

        Issue Links

          Activity

            People

              jason.price@mongodb.com Jason Price
              kelsey.schubert@mongodb.com Kelsey Schubert
              Jess Mokrzecki Jess Mokrzecki
              Garaudy Etienne, Kelsey Schubert
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                39 weeks, 3 days ago