SERVER-22672 Make moveChunk and shardCollection use the balancer

The moveChunk and shardCollection commands should not be calling directly
into the shards when they need to move chunks and instead they should use
the balancer. That way when the balancer moves to the CSRS primary, they
can just start making calls into it.

1 files changed, 0 insertions, 24 deletions

diff --git a/src/mongo/s/chunk.h b/src/mongo/s/chunk.h
index d9cf1886a6b..28bb1e519cc 100644
--- a/src/mongo/s/chunk.h
+++ b/src/mongo/s/chunk.h
@@ -37,7 +37,6 @@ namespace mongo {
 
 class ChunkManager;
 class ChunkType;
-class MigrationSecondaryThrottleOptions;
 class OperationContext;
 
 /**
@@ -132,29 +131,6 @@ public:
                                                                    SplitPointMode mode,
                                                                    size_t* resultingSplits) const;
 
-    //
-    // migration support
-    //
-
-    /**
-     * Issues a migrate request for this chunk
-     *
-     * @param to shard to move this chunk to
-     * @param chunSize maximum number of bytes beyond which the migrate should no go trhough
-     * @param writeConcern detailed write concern. NULL means the default write concern.
-     * @param waitForDelete whether chunk move should wait for cleanup or return immediately
-     * @param maxTimeMS max time for the migrate request
-     * @param res the object containing details about the migrate execution
-     * @return true if move was successful
-     */
-    bool moveAndCommit(OperationContext* txn,
-                       const ShardId& to,
-                       long long chunkSize,
-                       const MigrationSecondaryThrottleOptions& secondaryThrottle,
-                       bool waitForDelete,
-                       int maxTimeMS,
-                       BSONObj& res) const;
-
     /**
      * marks this chunk as a jumbo chunk
      * that means the chunk will be inelligble for migrates