ReplicaSetChangeNotifier functions should be noexcept

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.3.3
    • Affects Version/s: None
    • Component/s: None
    • Fully Compatible
    • 60
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Amirsaman Memaripour
            Reporter:
            Benjamin Caimano (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: