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

ReplicaSetChangeNotifier functions should be noexcept

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.3
    • Component/s: None
    • Backwards Compatibility:
      Fully Compatible
    • Linked BF Score:
      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

            Assignee:
            amirsaman.memaripour Amirsaman Memaripour
            Reporter:
            ben.caimano Benjamin Caimano (Inactive)
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: