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

Provide stack trace for ismaster failures in monitor

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.11.3, 2.12.0.rc0
    • Component/s: Connections
    • Labels:
      None

      Description

      When ismaster fails in a monitoring thread, the diagnostics currently looks like this:

       
      [2020/01/20 03:40:45.254] D, [2020-01-20T08:40:40.227285 #3397] DEBUG -- : MONGODB | Waiting for up to 3.00 seconds for servers to be scanned: #<Cluster topology=ReplicaSetNoPrimary[localhost:27017,localhost:27018,localhost:27019,name=repl0] servers=[#<Server address=localhost:27017 UNKNOWN>,#<Server address=localhost:27018 UNKNOWN>,#<Server address=localhost:27019 UNKNOWN>]>
      [2020/01/20 03:40:45.254] W, [2020-01-20T08:40:40.229096 #3397]  WARN -- : MONGODB | Failed to handshake with localhost:27018: ArgumentError: wrong number of arguments (given 2, expected 1)
      [2020/01/20 03:40:45.254] D, [2020-01-20T08:40:40.229145 #3397] DEBUG -- : MONGODB | Error running ismaster on localhost:27018: ArgumentError: wrong number of arguments (given 2, expected 1)
      [2020/01/20 03:40:45.254] W, [2020-01-20T08:40:40.229842 #3397]  WARN -- : MONGODB | Failed to handshake with localhost:27019: ArgumentError: wrong number of arguments (given 2, expected 1)
      [2020/01/20 03:40:45.254] D, [2020-01-20T08:40:40.229885 #3397] DEBUG -- : MONGODB | Error running ismaster on localhost:27019: ArgumentError: wrong number of arguments (given 2, expected 1)
      [2020/01/20 03:40:45.254] W, [2020-01-20T08:40:40.230038 #3397]  WARN -- : MONGODB | Failed to handshake with localhost:27017: ArgumentError: wrong number of arguments (given 2, expected 1)
      [2020/01/20 03:40:45.254] D, [2020-01-20T08:40:40.230073 #3397] DEBUG -- : MONGODB | Error running ismaster on localhost:27017: ArgumentError: wrong number of arguments (given 2, expected 1)
      

      The lack of stack trace makes it impossible to effectively diagnose and repair such problems. One must first reproduce the issue locally, then dump the stack trace manually or obtain it in some other way.

        Attachments

          Activity

            People

            Assignee:
            oleg.pudeyev Oleg Pudeyev
            Reporter:
            oleg.pudeyev Oleg Pudeyev
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: