Uploaded image for project: 'Java Driver'
  1. Java Driver
  2. JAVA-592

make server down log message less noisey

    • Type: Icon: Improvement Improvement
    • Resolution: Duplicate
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Cluster Management
    • None

      These error messages are much too noisy. The user does not need to see the stack trace because these messages are expected when a server is down and they originate from the RS monitor thread.

      The driver should look at the IOException and only display the message (take the source msg?).

      Less Noise

      06-30-2012 20:42:00 [ReplicaSetStatus:Updater] WARN com.mongodb.ReplicaSetStatus.mmsconfig1 [update:580] - Server seen down: server.something.com/10.137.128.62:27018 - bc:java.net.SocketTimeoutException: connect timed out

      Current

      06-30-2012 20:42:00 [ReplicaSetStatus:Updater] WARN com.mongodb.ReplicaSetStatus.mmsconfig1 [update:580] - Server seen down: server.something.com/10.137.128.62:27018
      java.io.IOException: couldn't connect to [server.something.com/10.137.128.62:27018] bc:java.net.SocketTimeoutException: connect timed out
      at com.mongodb.DBPort._open(DBPort.java:222) ~[mongo.jar:na]
      at com.mongodb.DBPort.go(DBPort.java:111) ~[mongo.jar:na]
      at com.mongodb.DBPort.go(DBPort.java:92) ~[mongo.jar:na]
      at com.mongodb.DBPort.findOne(DBPort.java:145) ~[mongo.jar:na]
      at com.mongodb.DBPort.runCommand(DBPort.java:156) ~[mongo.jar:na]
      at com.mongodb.ReplicaSetStatus$UpdatableNode.update(ReplicaSetStatus.java:507) ~[mongo.jar:na]
      at com.mongodb.ReplicaSetStatus$Updater.updateAll(ReplicaSetStatus.java:708) [mongo.jar:na]
      at com.mongodb.ReplicaSetStatus$Updater.run(ReplicaSetStatus.java:674) [mongo.jar:na]

            Assignee:
            rn@deftlabs.com Ryan Nitz
            Reporter:
            rn@deftlabs.com Ryan Nitz
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: