[JAVA-655] Reduce excessive logging when replica set primary is not reachable Created: 01/Oct/12  Updated: 25/Jun/13  Resolved: 25/Jun/13

Status: Closed
Project: Java Driver
Component/s: Cluster Management
Affects Version/s: 2.9.1
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates JAVA-836 Only log on server availability state... Closed
Backwards Compatibility: Fully Compatible

 Description   

When the primary is unreachable, the replica set health check happens every 10 ms instead of every 5000 ms (by default), and it logs at WARNING level for each server that's not reachable, flooding the logs.

Driver should reduce logging to at most once per second for each server.



 Comments   
Comment by Jeffrey Yemin [ 25/Jun/13 ]

Duplicates JAVA-836

Comment by Jeffrey Yemin [ 26/Feb/13 ]

There is no workaround at present, except to increase the health check interval when the primary is down, e.g.

-Dcom.mongodb.updaterIntervalNoMasterMS=1000

Comment by Michael Jacobs [ 26/Feb/13 ]

Is there a workaround for this issue? I am trying to avoid having the turn logging down for this component.

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