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

Add magic restore log path parameter and generate magic restore-specific logs

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Fully Compatible
    • v8.0
    • Repl 2024-05-13, Repl 2024-05-27, Repl 2024-06-10

      This ticket will add a new command line parameter (--magicRestoreLogPath) to specify where magic restore logs should go. This ticket will also likely need to investigate how we can log to two places at once, since the db will be writing to --logPath while magic restore needs to additionally output its logging to this separate file.

      It's still a little unclear exactly what logging should go specifically in the magic restore logs. It sounds like we want each step that was completed for magic restore, as well as any errors that occur. We should confirm with Cloud, but to start we can log "Starting [step]..." and "Finished [step]...". SERVER-85816 can sync up with Cloud and see what changes we need to make.

            Assignee:
            ali.mir@mongodb.com Ali Mir
            Reporter:
            ali.mir@mongodb.com Ali Mir
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: