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

Test magic restore specific logs without omitting test output

    • Type: Icon: Task Task
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Replication
    • Repl 2024-08-05, Repl 2024-08-19

      in SERVER-82908, we added logic that introduced a RESTORE log component, to allow Cloud to filter mongod logs for magic restore-specific log output. We added some logic in our replica set magic restore tests to test this filtering here. To do this, we needed to pass in the logpath parameter into the magic restore invocation here. This had the unintended side effect of omitting any test logs from the magic restore node while it's running, which makes it immensely difficult to debug.

      We should modify the logging portion of these tests to allow for test output, and find a way to test the "RESTORE" log component.

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

              Created:
              Updated: