SERVER-22027 Sharding should not retry killed operations

This change introduces a different interruption code (11602) which will be
used to kill operations during replication primary stepdown so the config
server retry logic can differentiate them from user-killed operations.

1 files changed, 6 insertions, 2 deletions

diff --git a/jstests/replsets/stepdown3.js b/jstests/replsets/stepdown3.js
index 9c3cf3d9544..65fa9d2df08 100644
--- a/jstests/replsets/stepdown3.js
+++ b/jstests/replsets/stepdown3.js
@@ -2,6 +2,8 @@
 //
 // This test requires the fsync command to force a secondary to be stale.
 // @tags: [requires_fsync]
+(function() {
+'use strict';
 
 var replTest = new ReplSetTest({ name: 'testSet', nodes: 2 });
 var nodes = replTest.startSet();
@@ -37,8 +39,8 @@ print("getlasterror; should assert or return an error, depending on timing");
 var gleFunction = function() {
     var result = master.getDB("test").runCommand({getLastError : 1, w: 2 , wtimeout :30000 });
     if (result.errmsg === "not master" ||
-            result.code == 10107 ||
-            result.code == 11601 /*interrupted*/ ) {
+        result.code == ErrorCodes.NotMaster ||
+        result.code == ErrorCodes.InterruptedDueToReplStateChange) {
         throw new Error("satisfy assert.throws()");
     }
     print("failed to throw exception; GLE returned: ");
@@ -54,3 +56,5 @@ assert.neq(0, exitCode, "expected replSetStepDown to close the shell's connectio
 // unlock and shut down
 printjson(locked.getDB("admin").fsyncUnlock());
 replTest.stopSet();
+
+})();