[JAVA-189] Warning thrown when one member of replica set is dhutdown Created: 14/Oct/10  Updated: 14/Oct/10  Resolved: 14/Oct/10

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

Type: Bug Priority: Minor - P4
Reporter: Alvin Richards (Inactive) Assignee: Eliot Horowitz (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

db version v1.7.2-pre-, pdfile version 4.5
git hash: 2a7f26cc8ff63a453215fa217869626ed8a7e0eb
sys info: Linux domU-12-31-39-06-79-A1 2.6.21.7-2.ec2.v1.2.fc8xen #1 SMP Fri Nov 20 17:48:28 EST 2009 x86_64 BOOST_LIB_VERSION=1_41
uptime: 676 seconds



 Description   

Problem:
After a replica set member is taken down, a connection that includes this node will get the following

Oct 14, 2010 4:49:46 AM com.mongodb.ReplicaSetStatus$Node update
WARNING: node down: 10.202.7.100:27000 java.io.IOException: couldn't connect to [/10.202.7.100:27000] bc:java.net.ConnectException: Connection refused

Reproduce:

  • create a 3 node replica
  • create a connection with all three members
  • set the connection to SalveOk
  • start to read
  • take down a node in the replica set
  • get the warning message

Business Case:

  • User Expereince
    This warning should probably be in the log, but probably not thrown to the client through the driver.


 Comments   
Comment by Alvin Richards (Inactive) [ 14/Oct/10 ]

./src/main/com/mongodb/ReplicaSetStatus.java: _logger.log( Level.WARNING , "node down: " + _addr + " " + root );

Will configure the log framework to output to file, rather than screen.

Comment by Eliot Horowitz (Inactive) [ 14/Oct/10 ]

That warning just stops there -won't get propogated to a user.

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