allow Shard::exhaustiveFindOnConfig to run on shards as well, and rename to Shard::exhaustiveFind

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Fix
    • Priority: Major - P3
    • None
    • Affects Version/s: 3.5.9
    • Component/s: Sharding
    • None
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For the first time, the config server needs to run a command (listCollections) against a shard that returns a cursor.

      The alternatives are to use DBClient::query or link establishCursors() and the ARM/ClusterClientCursor onto mongod, which is an entire summer 2017 intern project.

      We should replace the plumbing of ShardRemote::exhaustiveFind with establishCursors/ARM once they are linked into mongod, so that we can do a clean replace of the Fetcher with those with one change.

            Assignee:
            Esha Maharishi (Inactive)
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: