[DRIVERS-268] SDAM test for race condition when seed list host name does not match the one reported by ismaster Created: 07/Oct/15  Updated: 07/Oct/15  Resolved: 07/Oct/15

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

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

Issue Links:
Depends
Duplicate
duplicates DRIVERS-230 Remove from the topology a replica se... Closed

 Description   

See https://github.com/mongodb/specifications/blob/master/source/server-discovery-and-monitoring/server-discovery-and-monitoring.rst#updaterswithoutprimary.

Given the behavior specified here, it's possible for get-more/kill-cursor requests to fail in the following scenario:

  • Create MongoClient with a seed list with IP addresses for a replica set with host names as normal DNS names.
  • Execute a query with a non-primary read preference
  • Execute a get-more for that query

This can happen because server selection will succeed against a seed list host that reports itself as a secondary, but by the time the get-more executes, the primary has identified itself and the driver has replaced all the ip-address-specified seed list hosts with the host names from the primary's server description. The result is that server selection fails for the get-more, as the topology has "forgotten" about the seed list hosts.

There is now an automated test for this included in the SDAM specification. You'll pick it up with this tag.



 Comments   
Comment by Bernie Hackett [ 07/Oct/15 ]

This is a duplicate of DRIVERS-230.

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