Investigate changes in SERVER-100712: Prevent usage of $$CLUSTER_TIME in commands in standalone mode

XMLWordPrintableJSON

    • Type: Investigation
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Tools and Replicator

      Original Downstream Change Summary

      The patch adds an error code that could be raised in standalone mode.

      Description of Linked Ticket

      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.

            Assignee:
            Unassigned
            Reporter:
            Backlog - Core Eng Program Management Team
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: