SERVER-19410 Delete test verifying maxTimeMS tracking for mongos ops

1 files changed, 5 insertions, 15 deletions

diff --git a/jstests/sharding/max_time_ms_sharded.js b/jstests/sharding/max_time_ms_sharded.js
index a722dc02aa3..cc3d87505ec 100644
--- a/jstests/sharding/max_time_ms_sharded.js
+++ b/jstests/sharding/max_time_ms_sharded.js
@@ -84,25 +84,15 @@ assert.doesNotThrow(function() { cursor.next() },
 // Test that mongos correctly times out max time sharded getmore operations.  Uses
 // maxTimeNeverTimeOut to ensure mongod doesn't enforce a time limit.
 //
+// TODO: This is unimplemented.  A test for this functionality should be written as
+// part of the work for SERVER-19410.
+//
 
 configureMaxTimeNeverTimeOut("alwaysOn");
 
-// Positive test.  ~10s operation, 5s limit.  The operation takes ~10s because each shard processes
-// 25 batches of ~200ms each, and mongos never runs getmore in parallel on shards.
-// TODO: Re-enable once SERVER-19410 is implemented.
-/*
-cursor = coll.find({$where: function() { sleep(100); return true; }});
-cursor.batchSize(2);
-cursor.maxTimeMS(5*1000);
-assert.doesNotThrow(function() { cursor.next(); },
-                    [],
-                    "did not expect mongos to time out first batch of query");
-assert.throws(function() { cursor.itcount(); },
-              [],
-              "expected mongos to abort getmore due to time limit");
-*/
+// Positive test.  TODO: see above.
 
-// Negative test.  Same as above (~10s operation), with a high (1-day) limit.
+// Negative test.  ~10s operation, with a high (1-day) limit.
 cursor = coll.find({$where: function() { sleep(100); return true; }});
 cursor.batchSize(2);
 cursor.maxTimeMS(1000*60*60*24);