SERVER-73858 add js test for geo 2d index options conflict during initial sync

(cherry picked from commit 3d7dfa8ad0606362be739effd43dd01b5b8048d9)

1 files changed, 101 insertions, 0 deletions

diff --git a/jstests/replsets/initial_sync_geo_index_conflict.js b/jstests/replsets/initial_sync_geo_index_conflict.js
new file mode 100644
index 00000000000..152fe6df2e4
--- /dev/null
+++ b/jstests/replsets/initial_sync_geo_index_conflict.js
@@ -0,0 +1,101 @@
+/**
+ * Asserts that applying a single-phase createIndexes oplog entry for a 2d geo index with a
+ * floating point bits field doesn't cause initial-sync to fail if there is an existing index
+ * spec with a rounded bits value.
+ * This may happen if the index was first created on the primary when the collection was empty.
+ * The initial sync node would have to clone the index with the rounded value provided by
+ * listIndexes and subsequently re-apply the single-phase index build entry.
+ *
+ * @tags: [
+ *     requires_fcv_70,
+ * ]
+ */
+
+(function() {
+'use strict';
+
+load('jstests/libs/fail_point_util.js');
+load('jstests/noPassthrough/libs/index_build.js');
+
+function runTest(numDocs) {
+    const dbName = 'test';
+    const collectionName = 'coll-' + numDocs;
+
+    // Start one-node repl-set.
+    const rst = new ReplSetTest({nodes: 1});
+    rst.startSet();
+    rst.initiate();
+    const primary = rst.getPrimary();
+    const primaryDB = primary.getDB(dbName);
+    const primaryColl = primaryDB.getCollection(collectionName);
+
+    // Add a secondary.
+    const secondary = rst.add({
+        rsConfig: {votes: 0, priority: 0},
+        setParameter: {
+            numInitialSyncAttempts: 1,
+            // Increase log level to see debug messages for "Ignoring indexing error".
+            logComponentVerbosity: tojsononeline({replication: 1, storage: 1}),
+        },
+    });
+
+    // While the secondary is hung, we create the same index multiple times to
+    // reproduce the interaction between single and two phase index builds on the
+    // same index.
+    const failPoint = configureFailPoint(secondary, 'initialSyncHangBeforeCopyingDatabases');
+    rst.reInitiate();
+    failPoint.wait();
+
+    try {
+        // Create the index using the empty collection fast path. The index build should be
+        // replicated in a single createIndexes oplog entry. A floating point 'bits' option would be
+        // converted to a whole number (12 in this case) when initial sync recreates the indexes on
+        // the collection during the cloning phase. However, the oplog entry generated would still
+        // contain the floating point value 12.345.
+        assert.commandWorked(primaryColl.createIndex({a: '2d'}, {bits: 12.345}));
+
+        for (let i = 0; i < numDocs; i++) {
+            assert.commandWorked(primaryColl.insert({_id: i, a: i}));
+        }
+    } finally {
+        // Resume initial sync. The createIndexes oplog entry will be applied.
+        failPoint.off();
+    }
+
+    // Initial sync fails due to unhandled IndexOptionsConflict error on empty collection.
+    if (numDocs == 0) {
+        assert.soon(function() {
+            return rawMongoProgramOutput().search(
+                       /Fatal assertion.*40088.*IndexOptionsConflict.*name.*a_2d/) >= 0;
+        });
+
+        rst.stop(secondary, /*signal=*/undefined, {allowedExitCode: MongoRunner.EXIT_ABRUPT});
+        rst.stopSet();
+        return;
+    }
+
+    // Wait for initial sync to finish.
+    rst.awaitSecondaryNodes();
+
+    // We handle single phase indexing errors in different parts of the oplog application logic
+    // depending on whether the collection is empty at the time. Hence, the different log message
+    // IDs.
+    const expectedLogMsgId = (numDocs === 0 ? 7261800 : 4718200);
+    checkLog.containsJson(secondary, expectedLogMsgId, {
+        namespace: primaryColl.getFullName(),
+        spec: (spec) => {
+            jsTestLog('Checking index spec in oplog application log message: ' + tojson(spec));
+            return spec.name === 'a_2d';
+        }
+    });
+
+    // We rely on the replica set test fixture shutdown to compare the collection contents
+    // (including index specs) between the two nodes in the cluster.
+    rst.stopSet();
+}
+
+// We test both empty and non-empty collections because these are handled slightly differently
+// in the oplog application code.
+runTest(0);
+runTest(1);
+})();