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

get cursor logic used to find docs to clone (in migration) is not same as in removeRange

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.15, 4.0.13, 4.2.1, 4.3.1
    • Component/s: Sharding
    • Labels:
      None
    • Backwards Compatibility:
      Minor Change
    • Operating System:
      ALL
    • Backport Requested:
      v4.2, v4.0, v3.6
    • Sprint:
      Sharding 2018-09-24, Sharding 2018-10-08, Sharding 2018-10-22, Sharding 2018-12-03, Sharding 2018-12-17, Sharding 2018-12-31, Sharding 2019-01-14, Sharding 2019-01-28, Sharding 2019-02-11, Sharding 2019-02-25, Sharding 2019-03-11, Sharding 2019-03-25, Sharding 2019-09-09

      Description

      In storeClonedLocs(), we use nsd->findIndexByPrefix(), in removeRange() we use nsd->findIndexByKeyPattern(). This may be a problem if the user has multiple indexes prefixed by the shard key and some of the indexes are sparse.

        Attachments

          Issue Links

          is duplicated by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-18226 shardCollection command can orphan documents that are missing shard key if sparse index present

          • Major - P3 - Major loss of function.
          • Closed
          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-18226 shardCollection command can orphan documents that are missing shard key if sparse index present

          • Major - P3 - Major loss of function.
          • Closed

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: