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

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.6.15, 4.0.13, 4.2.1, 4.3.1
    • Affects Version/s: None
    • Component/s: Sharding
    • None
    • Minor Change
    • ALL
    • v4.2, v4.0, v3.6
    • 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
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            kevin.pulo@mongodb.com Kevin Pulo
            Reporter:
            greg_10gen Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: