> If there is another connection open, I would prefer > EnsurePoolIsPopulatedAsync() to occur in the background
That is what you suggested with the task scheduler, right? (Maybe I'm just understanding you wrong here, I'm especially not sure about how a back-off delay could work.) I agree that doing this in the background makes more sense in this case, but I won't be able to implement this in time for 3.4.1 and I also prefer not to change too much at the same time if it's not necessary. So, I would like to just create a ticket for this issue and then try to implement it for 3.4.2. Adding a delay and a counter here to the loop would be easy to implement. So, if you think that's already an improvement then I can add that. > fail as fast as possible. That should be the current situation as we don't catch any exception here. So it fails when one connection establishment fails. [ Full content available at: https://github.com/apache/tinkerpop/pull/1077 ] This message was relayed via gitbox.apache.org for [email protected]
