Unresolved Connection

[aricart]

Proposed change

Connections that never resolved because options have unlimited reconects/wait on first connect etc don't provide any information on why the connection is not resolved

Use case

this is really just a debug scenario.

Contribution

Not sure what the solution is - effectively connections that don't fail after a certain number of retries, are subject to thrashing.
Perhaps the correct thing to do is provide a deadline property that is only applicable to first connect. If the connection doesn't establish within this amount of time, the connection should reject with whatever error is happening.

For example (bad creds/authenticator implementation is simply ignored on an always reconnect type scenario)

#282

[aricart]

@caspervonb just wondering what your thoughts are - I think this is just the case of applying a deadline to the first connection process when maxReconnects is -1 or bad credential ignores are specified