Post analysis on the above mentioned issue, we able to see that the ServerTuple value in the AbstractMultiServerCluster$ServerTuple object which is updated from isMaster result set has the correct cluster information, where as, the addressToServerTupleMap from MongoClientImpl object doesn’t have the correct info for the primary shard after ClusterDescriptionChangedEvent. the Secondary information was correctly populated as expected.
This behavior is inconsistent across all the shard members on the specific container.
Please let us know, how to get the implementation on ClusterListener.clusterDescriptionChanged(ClusterDescriptionChangedEvent) method.
Also we are not sure why this behaviour is consistent, which fails all the DB transaction towards this ReplicaSet.
Hi Team, Good Morning, on further analysis on the acquiring the primary during write operations, when primary is not available, the expectations is the clusterDescription.getPrimaries() should return empty list, but instead it returns TimeoutException
Hi Team, Good Morning, Please let us know for any info on this specific behavior from Mongo Client Driver… this would be helpful for us on the identifying the root cause and handle it in our client side. Thanks in Advance/!