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
You create session of it that does not actually connects to the cluster, but rather just starting this proccess.
If you are trying to execute query on such session, if it is not ready yeat it will throw you an NotReady error
Have an API that allows you to know if session is ready to execute queries
This API will make easier to develop apps for k8s, creating session on pod initialization and report connection status via liveness and readiness probs
The text was updated successfully, but these errors were encountered:
This is great. Separating initialization and actual connections solves a number of production edge cases. Couple of considerations:
CreateSession() won't block and fail and will try to establish a connection in the background?
CreateSession() won't connect initially, but only when it's used. For example, when doing a .Query()?
Either should be fine, but 2 gives fine grained control on the behaviour, where it's possible to have config to try and connect in the background immediately or to "lazy" connect only when the session is used for querying.
Idea is the following:
NotReady
errorThis API will make easier to develop apps for
k8s
, creating session on pod initialization and report connection status vialiveness
andreadiness
probsThe text was updated successfully, but these errors were encountered: