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

Change fassert and invariant to fassertNoTrace when failing to startup

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Replication
    • None
    • Replication
    • 6

    Description

      Currently, when we try to restart an empty standalone, it will fail trying to recover, and we fail it with an fatal assertion.

      Additionally, when we try to restart a replica set node with the recoverFromOplogAsStandalone parameter set, it also fails. We fail it with an invariant here.

      We should consider changing the fassert and invariant to fassertNoTrace to avoid core dumping and stack tracing, since the issue is with the startup parameter/the data the server has been fed, and not an issue with the server logic itself.

      Attachments

        Activity

          People

            backlog-server-repl Backlog - Replication Team
            huayu.ouyang@mongodb.com Huayu Ouyang
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: