-
Type: Bug
-
Resolution: Done
-
Priority: Unknown
-
None
-
Affects Version/s: None
-
Component/s: Test Failure
Looks like the failpoint is failing due to: "The server is being accessed through a load balancer, but this driver does not have load balancing enabled"
[2021/10/08 20:38:43.098] FAILURE: com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting to connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=11549-mongo-java-driver-shard-00-02.2tzoa.mongodb-dev.net:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoCommandException: Command failed with error 354 (LoadBalancerSupportMismatch): 'The server is being accessed through a load balancer, but this driver does not have load balancing enabled' on server 11549-mongo-java-driver-shard-00-02.2tzoa.mongodb-dev.net:27017. The full response is {"ok": 0, "errmsg": "The server is being accessed through a load balancer, but this driver does not have load balancing enabled", "code": 354, "codeName": "LoadBalancerSupportMismatch"}}}] (com.mongodb.MongoTimeoutException) [2021/10/08 20:38:43.098] com.mongodb.MongoTimeoutException: Timed out after 30000 ms while waiting to connect. Client view of cluster state is {type=UNKNOWN, servers=[{address=11549-mongo-java-driver-shard-00-02.2tzoa.mongodb-dev.net:27017, type=UNKNOWN, state=CONNECTING, exception={com.mongodb.MongoCommandException: Command failed with error 354 (LoadBalancerSupportMismatch): 'The server is being accessed through a load balancer, but this driver does not have load balancing enabled' on server 11549-mongo-java-driver-shard-00-02.2tzoa.mongodb-dev.net:27017. The full response is {"ok": 0, "errmsg": "The server is being accessed through a load balancer, but this driver does not have load balancing enabled", "code": 354, "codeName": "LoadBalancerSupportMismatch"}}}] [2021/10/08 20:38:43.098] at com.mongodb.internal.connection.BaseCluster.getDescription(BaseCluster.java:181) [2021/10/08 20:38:43.098] at com.mongodb.internal.connection.SingleServerCluster.getDescription(SingleServerCluster.java:41) [2021/10/08 20:38:43.098] at com.mongodb.client.internal.MongoClientDelegate.getConnectedClusterDescription(MongoClientDelegate.java:144) [2021/10/08 20:38:43.098] at com.mongodb.client.internal.MongoClientDelegate.createClientSession(MongoClientDelegate.java:101) [2021/10/08 20:38:43.098] at com.mongodb.client.internal.MongoClientDelegate$DelegateOperationExecutor.getClientSession(MongoClientDelegate.java:291) [2021/10/08 20:38:43.098] at com.mongodb.client.internal.MongoClientDelegate$DelegateOperationExecutor.execute(MongoClientDelegate.java:183) [2021/10/08 20:38:43.098] at com.mongodb.client.internal.MongoDatabaseImpl.executeCommand(MongoDatabaseImpl.java:195) [2021/10/08 20:38:43.098] at com.mongodb.client.internal.MongoDatabaseImpl.runCommand(MongoDatabaseImpl.java:164) [2021/10/08 20:38:43.098] at com.mongodb.client.internal.MongoDatabaseImpl.runCommand(MongoDatabaseImpl.java:159) [2021/10/08 20:38:43.098] at com.mongodb.client.internal.MongoDatabaseImpl.runCommand(MongoDatabaseImpl.java:149) [2021/10/08 20:38:43.098] at com.mongodb.client.FailPoint.enable(FailPoint.java:63) [2021/10/08 20:38:43.098] at com.mongodb.client.FailPoint.enable(FailPoint.java:51) [2021/10/08 20:38:43.098] at com.mongodb.client.ServerDiscoveryAndMonitoringProseTests.monitorsSleepAtLeastMinHeartbeatFreqencyMSBetweenChecks(ServerDiscoveryAndMonitoringProseTests.java:259)