summaryrefslogtreecommitdiff
path: root/jstests/replsets/tenant_migration_causal_consistency_commit_optime_before_last_cloning_optime.js
diff options
context:
space:
mode:
Diffstat (limited to 'jstests/replsets/tenant_migration_causal_consistency_commit_optime_before_last_cloning_optime.js')
-rw-r--r--jstests/replsets/tenant_migration_causal_consistency_commit_optime_before_last_cloning_optime.js5
1 files changed, 5 insertions, 0 deletions
diff --git a/jstests/replsets/tenant_migration_causal_consistency_commit_optime_before_last_cloning_optime.js b/jstests/replsets/tenant_migration_causal_consistency_commit_optime_before_last_cloning_optime.js
index bbb3640c806..242566c2bac 100644
--- a/jstests/replsets/tenant_migration_causal_consistency_commit_optime_before_last_cloning_optime.js
+++ b/jstests/replsets/tenant_migration_causal_consistency_commit_optime_before_last_cloning_optime.js
@@ -2,9 +2,14 @@
* Verify that causal consistency is respected if a tenant migration commits with an earlier optime
* timestamp than the latest optime associated with cloning on the recipient.
*
+ * TODO (SERVER-61231): This test currently relies on a TenantCollectionCloner failpoint, which is
+ * not used by shard merge, but the behavior we are testing here is likely still relevant. Adapt
+ * for shard merge.
+ *
* @tags: [
* incompatible_with_eft,
* incompatible_with_macos,
+ * incompatible_with_shard_merge,
* incompatible_with_windows_tls,
* requires_majority_read_concern,
* requires_persistence,