SERVER-34628 Really remove appendCommandStatus

All remaining callers are transitioned to some form of usassert. This was done
with an elaborate set of vim macros to make this tractable. Therefore it
should not be considered an example of the best way to write new code, just as
an improvement on what was there before. In particular, I couldn't easily
remove Status's that are named then only used once in uassertStatusOK, nor
could I convert the pattern of checking a StatusWith<T>'s getStatus() then
calling getValue() to just call uassertStatusOK(returnsStatusWith()).

1 files changed, 0 insertions, 10 deletions

diff --git a/src/mongo/db/s/move_chunk_command.cpp b/src/mongo/db/s/move_chunk_command.cpp
index cb1fa99fc2c..80b31ba76c7 100644
--- a/src/mongo/db/s/move_chunk_command.cpp
+++ b/src/mongo/db/s/move_chunk_command.cpp
@@ -145,16 +145,6 @@ public:
         } else {
             status = scopedMigration.waitForCompletion(opCtx);
         }
-
-        if (status == ErrorCodes::ChunkTooBig) {
-            // This code is for compatibility with pre-3.2 balancer, which does not recognize the
-            // ChunkTooBig error code and instead uses the "chunkTooBig" field in the response,
-            // and the 3.4 shard, which failed to set the ChunkTooBig status code.
-            // TODO: Remove after 3.6 is released.
-            result.appendBool("chunkTooBig", true);
-            return CommandHelpers::appendCommandStatus(result, status);
-        }
-
         uassertStatusOK(status);
 
         if (moveChunkRequest.getWaitForDelete()) {