[JAVA-380] Very verbose error messages (continuous) on replica set member failure Created: 13/Jun/11  Updated: 17/Jul/15  Resolved: 03/Aug/12

Status: Closed
Project: Java Driver
Component/s: Monitoring
Affects Version/s: None
Fix Version/s: 2.9.0

Type: Improvement Priority: Major - P3
Reporter: Greg Studer Assignee: Ryan Nitz
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Driver 2.6.3


Attachments: Java Source File Test.java     Text File stacktraces.txt    
Issue Links:
Duplicate
is duplicated by JAVA-592 make server down log message less noisey Closed
Related

 Description   

When members go down (which is expected to happen at some point) there are very verbose error messages, see included .txt file for a 3-node replica set, being shut down one node at a time. Maybe no stack trace by default, or after the first error?



 Comments   
Comment by Jeffrey Yemin [ 29/Aug/12 ]

Closing as part of 2.9.0 release process.

Comment by auto [ 10/Jul/12 ]

Author:

{u'date': u'2012-07-03T07:28:50-07:00', u'name': u'Ryan', u'email': u'rgnitz@gmail.com'}

Message: fixed verbosity of expected log messages and made _ok volatile - JAVA-380
Branch: ReadPrefs
https://github.com/mongodb/mongo-java-driver/commit/ea1f39668f16bbfde4fde147d0f31cf8ad3ec719

Comment by Ryan Nitz [ 03/Jul/12 ]

Jeff code reviewed the change.

Here is an example of the new format:

07-03-2012 15:09:48 [ReplicaSetStatus:Updater] G: WARN com.mongodb.ReplicaSetStatus [update:603] - Server seen down: /127.0.0.1:27018 - java.io.IOException - message: couldn't connect to [/127.0.0.1:27018] bc:java.net.SocketTimeoutException: connect timed out

Comment by auto [ 03/Jul/12 ]

Author:

{u'date': u'2012-07-03T07:28:50-07:00', u'name': u'Ryan', u'email': u'rgnitz@gmail.com'}

Message: fixed verbosity of expected log messages and made _ok volatile - JAVA-380
Branch: master
https://github.com/mongodb/mongo-java-driver/commit/ea1f39668f16bbfde4fde147d0f31cf8ad3ec719

Generated at Thu Feb 08 08:52:09 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.