Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-35130

view_catalog_cycle_lookup.js failed in the newly created concurrency_replication_causal_consistency suite

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.0
    • Sprint:
      Storage NYC 2018-06-04, Storage NYC 2018-06-18

      Description

      The evergreen patch shows that there could be a view cycle when we perform reads on the secondary node. Since collMod command won't succeed on the primary if it forms a cycle, this could be a bug for secondary reads.

      Update:
      Basically, view catalog could reload (loading view definitions from system.views to in-memory data structure) whenever a read comes and there is discrepancy between persistent version and in-memory version of view definition, even during oplog application. Thus, secondary reads could see inconsistent state of view catalog.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: