|
Hi satish.anupindi@aexp.com
- The driver load balances all available secondaries. If no secondaries are available, it directs all requests to the primary.
- It's possible that it's a driver bug, but if so this would be the first report. A few things to check:
- Enable DEBUG logging in the driver for the org.mongodb.driver.protocol component. That will log messages like: "Sending command '%s' with request id %d to database %s on connection [%s] to server %s" so you can see where requests are being routed
- Check the server logs to see where requests are actually originating.
- Check your MongoClient settings to make sure you're not accidentally leaving the read preference as non-primary. Note also that the read preference can be change per MongoCollection or MongoDatabase, so it's possible that the primary read preference is being overridden somewhere else in your application.
Just to let you know this project is for Java driver bugs or feature requests. The best place for questions regarding MongoDB usage or the Java driver specifics is the mongodb-user mailing list or stackoverflow as you will reach a broader audience there. If your business requires an answer from MongoDB within a time frame then we do offer production support.
If you do follow up via one of the options above please post a link and I will follow the conversation there.
|