Uploaded image for project: 'Ruby Driver'
  1. Ruby Driver
  2. RUBY-1549

Correctly handle monitoring thread death in constructor sdam wait

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 2.7.0.rc0
    • Spec Comp
    • None

    Description

      1357 had a slight problem which was more clearly exposed by 1517, in that if any servers in the seed list ended up removed from topology (such as due to a me mismatch), the constructor will wait up to server selection timeout because the monitoring thread got killed before it could write the heartbeat completion time to the server.

      The fix is to write heartbeat completion time prior to invoking sdam flow by publishing the description change event.

      Attachments

        Issue Links

          Activity

            People

              oleg.pudeyev@mongodb.com Oleg Pudeyev
              oleg.pudeyev@mongodb.com Oleg Pudeyev
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: