You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After much help from @iansrobinson, we are using this library in our DEV and PROD environments.
One thing I'm deliberating how to handle is closing the GraphTraversalSource we've built, as well as the ClusterEndpointsRefreshAgent. They both expose a close() method, but I'm wondering if we have some elegant way to "wait" for pending queries, without holding state. The service should stop receiving requests from the load balancer on rolling a new version (or pod restart), so we can rely on that, but I'm wondering if something nice is also exposed.
The text was updated successfully, but these errors were encountered:
After much help from @iansrobinson, we are using this library in our DEV and PROD environments.
One thing I'm deliberating how to handle is closing the
GraphTraversalSource
we've built, as well as theClusterEndpointsRefreshAgent
. They both expose aclose()
method, but I'm wondering if we have some elegant way to "wait" for pending queries, without holding state. The service should stop receiving requests from the load balancer on rolling a new version (or pod restart), so we can rely on that, but I'm wondering if something nice is also exposed.The text was updated successfully, but these errors were encountered: