orlandos-nl / MongoKitten

Describe the bug

In MongoCluster, resolving of SRV hostnames is kicked off in .init(lazyConnectingTo:logger:eventLoopGroup:). This happens in asynchronously in a task:

MongoKitten/Sources/MongoClient/Cluster.swift

Lines 167 to 172 in 0ca7b30

    
           Task { 
        
               // Kick off the connection process 
        
               try await resolveSettings() 
        
               scheduleDiscovery() 
        
           }

Because the result of this (which happens in resolveSettings) is not awaited before creating connections, a race condition exists: connections that are lazily created before the hostname resolution is complete, will connect to the wrong hostname.

	Task {
	// Kick off the connection process
	try await resolveSettings()

	scheduleDiscovery()
	}

Race condition in MongoCluster when using lazy connection to SRV hostname