If I insert a Timestamp(0,0) value in some collection, the following things happen:
1. If $$CLUSTER_TIME did not exist previously because it is not a replica set or a sharded cluster, it now exists.
2. The value of $CLUSTER_TIME seems stuck to the time of the latest insertion of Timestamp(0,0) , until another such insertion occurs.
- is depended on by
-
COMPASS-9336 Investigate changes in SERVER-100712: Prevent usage of $$CLUSTER_TIME in commands in standalone mode
-
- Needs Triage
-
-
TOOLS-3882 Investigate changes in SERVER-100712: Prevent usage of $$CLUSTER_TIME in commands in standalone mode
-
- Needs Triage
-
- is related to
-
SERVER-100714 Do not use Timestamp(0,0) in CBR tests
-
- Closed
-
- related to
-
SERVER-104756 Exclude tests with $CLUSTER_TIME from suites comparing standalone and non-standalone topology
-
- Closed
-
-
SERVER-102499 Do not use cluster time in standalone mode
-
- Needs Scheduling
-
-
SERVER-88750 Add "bypassEmptyTsReplacement" param to insert, update, findAndModify, and bulkWrite
-
- Closed
-
-
SERVER-104560 Create utility functions that return the current server topology
-
- Open
-