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

Verify global index ddl oplog entry namespace

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • 1

      The oplog entry namespace for Global Index DDLs is currently being set to the command namespace We should reevaluate if this is actually the namespace we want to be replicating or not.

      If global index operations are expected to be run as retryable writes (which seems to be the case based on the op_observer_impl function linked) there could be some issues if we use the command namespace instead of the globalIndexNss. In SERVER-80699 we are tracking all affectedNamespaces for retryable writes using the list to determine if we need to consider a session for chunk migration or not. Using the command namespace could cause the entries to not be migrated, so we want to make sure this scenario cannot happen or is fixed

            Assignee:
            backlog-server-catalog-and-routing [DO NOT USE] Backlog - Catalog and Routing
            Reporter:
            sean.zimmerman@mongodb.com Sean Zimmerman
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: