Prohibit operations on system.profile inside of transactions

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.4.0-rc6, 4.7.0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v4.4
    • Execution Team 2020-04-20, Execution Team 2020-05-04, Execution Team 2020-05-18
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Presently, system.profile is the only non-replicated collection that can be read from in a multi-document transaction (we exclude operations on local from transactions).

      This collection does not have a commit timestamp with which to set its minimum visible snapshot. This collection also does not require an ID index build, hence will not have its minimum visible snapshot set to the cluster time via the ID index build. It can therefore not have a minimum visible snapshot be set.

      We believe the best solution for this is to prohibit operations on the system.profile collection inside of a transaction.

              Assignee:
              Maria van Keulen
              Reporter:
              Maria van Keulen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: