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

ReplicaSetChangeNotifier functions should be noexcept

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 4.3.3
    • None
    • None
    • Fully Compatible
    • 60

    Description

      The core handler functions for the RSCN would disrupt the entire scanning thread if an exception were to pop out. They should be noexcept. This also means we should look at ReplicaSetChangeNotifier::Listener subclasses and see if we need to try-catch. I suspect that the Mongos/ConfigServer update subclasses do need a try-catch and the ConnectionPool controller subclass does not.

      Attachments

        Activity

          People

            amirsaman.memaripour@mongodb.com Amirsaman Memaripour
            ben.caimano@mongodb.com Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: