-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Catalog and Routing
-
Fully Compatible
-
CAR Team 2025-10-27
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Evaluate if we can use kStrictlyNotIdempotent instead of kNoRetry in the following cases:
- FindAndModifyCmd::_runCommand (cluster_find_and_modify_cmd.cpp)
- ClusterWriteCmd::commandOpWrite (cluster_write_cmd.cpp)
- ClusterWriteWithoutShardKeyCmd::Invocation::typedRun (cluster_write_without_shard_key_cmd.cpp)
- ClusterWriteWithoutShardKeyCmd::Invocation::explain (cluster_write_without_shard_key_cmd.cpp)
- ClusterQueryWithoutShardKeyCmd::Invokation::typedRun (cluster_query_without_shard_key_cmd.cpp)
- ClusterQueryWithoutShardKeyCmd::Invokation::explain (cluster_query_without_shard_key_cmd.cpp)
There is also cluster_kill_op, but we think it's unlikely we want to retry this command. We should also evaluate if this is the case.