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
regarding the infamous Azure TCP idle connection drop problem (crate/crate#10779), I would like to give you a heads-up in the context of Kubernetes operators (Azure/AKS#1877).
According to dev-obs/actus#272, AKS clusters running Kubernetes v1.19+ are currently receiving a bugfix
The AKS control plane will always send RST for idle connections after 4min.
So, this will probably mitigate any problems in this regard for connections through kubernetes-asyncio.
With kind regards,
Andreas.
P.S.: However, I don't know whether any connections through aiopg might still be affected.
The text was updated successfully, but these errors were encountered:
So, while I want to apologize that I didn't look into how socket options can be set directly like crate/crate-python#374 when using aiopg, I am inclined to believe that the pool_recycle option of aiopg.create_pool() might help us here:
pool_recycle (float) – number of seconds after which connection is recycled, helps to deal with stale connections in pool, default value is -1, means recycling logic is disabled.
Dear @MarkusH, @chaudum, @lukasbals and @Taliik,
regarding the infamous Azure TCP idle connection drop problem (crate/crate#10779), I would like to give you a heads-up in the context of Kubernetes operators (Azure/AKS#1877).
According to dev-obs/actus#272, AKS clusters running Kubernetes v1.19+ are currently receiving a bugfix
So, this will probably mitigate any problems in this regard for connections through
kubernetes-asyncio
.With kind regards,
Andreas.
P.S.: However, I don't know whether any connections through
aiopg
might still be affected.The text was updated successfully, but these errors were encountered: