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
Since switching to the new Azure native FS in our environments we've been seeing a lot of connection leaks and java.lang.IllegalStateException: Unbalanced enter/exit exceptions. The native FS seemed to cause stability issues in earlier versions of Trino (like in Trino 452) so we had switched off back to legacy but in version 460 where it's required it seems ok. I'm not sure if our past stability issues in other versions were unrelated to the leaks or they're now mitigated due to other changes.
We get the following exceptions when running most queries:
WARNOkHttpConnectionPoolokhttp3.OkHttpClientAconnectiontohttps://<domain>.blob.core.windows.net/ was leaked. Did you forget to close a response body? To see where this was allocated, set the OkHttpClient logger level to FINE: Logger.getLogger(OkHttpClient.class.getName()).setLevel(Level.FINE);
And I believe we get the following stack traces as a result of turning logging up:
I'm not able to reproduce the issue 100% of the time but it's nonetheless very easy to reproduce on our end. Querying any catalog using the native Azure FS for a small amount of data (like 1000+ rows) will almost certainly throw the Unbalanced enter/exit exceptions later followed by connection leak warnings. For example, since switching to trino 460 on October 16th in one of our clusters, we've had roughly 430k queries, 157k unbalanced enter/exit exceptions and 107k connection leak warnings in our logs.
I tried investigating the issue on my own but it's not really clear to me what's happening or where the issue is between Trino/Azure SDK/OkHttp. Different versions of Trino and Azure SDK all exhibit the same problem in my experience.
The text was updated successfully, but these errors were encountered:
@cccs-nik you're reporting some issue that's not manifesting itself anymore since 460? Is it worth investigating? It might have been an issue in the Azure SDK, and we're constantly upgrading it to the latest version.
@nineinchnick Sorry for the confusion, what I meant was that we are not crashing as a result of using the native Azure FS anymore in 460, but the Unbalanced enter/exits and connection leak warnings are most definitely still happening.
Since switching to the new Azure native FS in our environments we've been seeing a lot of connection leaks and java.lang.IllegalStateException: Unbalanced enter/exit exceptions. The native FS seemed to cause stability issues in earlier versions of Trino (like in Trino 452) so we had switched off back to legacy but in version 460 where it's required it seems ok. I'm not sure if our past stability issues in other versions were unrelated to the leaks or they're now mitigated due to other changes.
We get the following exceptions when running most queries:
Followed by connection leak warnings:
And I believe we get the following stack traces as a result of turning logging up:
I'm not able to reproduce the issue 100% of the time but it's nonetheless very easy to reproduce on our end. Querying any catalog using the native Azure FS for a small amount of data (like 1000+ rows) will almost certainly throw the Unbalanced enter/exit exceptions later followed by connection leak warnings. For example, since switching to trino 460 on October 16th in one of our clusters, we've had roughly 430k queries, 157k unbalanced enter/exit exceptions and 107k connection leak warnings in our logs.
I tried investigating the issue on my own but it's not really clear to me what's happening or where the issue is between Trino/Azure SDK/OkHttp. Different versions of Trino and Azure SDK all exhibit the same problem in my experience.
The text was updated successfully, but these errors were encountered: