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

Rolling index builds will log buildUUIDs in the createIndexCmd logs

    • Type: Icon: Bug Bug
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • ALL
    • Storage Execution 2025-03-17
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      Rolling index builds do not have buildUUIDs, this is only set for two-phase, or replicated, index builds.
      However, when we issue the create index command we unconditionally generate a buildUUID that we end up logging, even if we do not use this uuid.
      This can lead to confusing behavior where in some logs a rolling index build will have a buildUUID of null and in others it will have a buildUUID as if it were a replicated index build.

            Assignee:
            Unassigned Unassigned
            Reporter:
            damian.wasilewicz@mongodb.com Damian Wasilewicz
            Votes:
            1 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: