From 543ad92616e96d54894f84dafb4c2904c1a032c3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Marcos=20Jos=C3=A9=20Grillo=20Ramirez?= Date: Tue, 21 Feb 2023 10:02:21 +0000 Subject: [PATCH] SERVER-52989 Remove TODO from shard_aware_init.js jstest --- jstests/sharding/shard_aware_init.js | 4 ---- 1 file changed, 4 deletions(-) diff --git a/jstests/sharding/shard_aware_init.js b/jstests/sharding/shard_aware_init.js index 92533e422f8..c4db788bd8a 100644 --- a/jstests/sharding/shard_aware_init.js +++ b/jstests/sharding/shard_aware_init.js @@ -25,10 +25,6 @@ var waitForPrimary = function(conn) { * initial write to the admin.system.version collection is fully flushed out of the oplog before * restarting. That allows our standalone corrupting update to see the write (and cause us to * fail on startup). - * - * TODO: Remove awaitVersionUpdate after SERVER-41005, where we figure out how to wait until - * after replication is started before reading our shard identity from - * admin.system.version */ var runTest = function(mongodConn, configConnStr, awaitVersionUpdate) { var shardIdentityDoc = {