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
What happened: We are running on Dremio Enterprise v20.2.3. We use Snowflake ARP connector for Snowflake connectivity (dremio-snowflake-plugin-20.1.0.jar + snowflake-jdbc-3.13.5.jar) and use Snowflake Service Account to connect to those warehouse.
We have been notified by Snowflake team that every Snowflake Source in Dremio is creating sessions every 60 secs in Snowflake environment and we are trying to understand if this is the expected behavior. Note, these are not the Metadata refresh that Dremio does every 1 Hour for dataset discovery & dataset details fetch.
What you expected to happen: We would like to know if there is a way to stop this behavior. At this point am not sure if these sessions are consuming any Snowflake resources or not.
How to reproduce it (as minimally and precisely as possible): NA
Anything else we need to know?: Second part to this ticket is, Metadata refresh is essentially consuming Snowflake resources - Are there any ways to prevent it except increasing the Metadata Refresh frequency!
Details:
Dremio version (Help > About from the UI): 20.2.3
Profile zip:
server.log:
The text was updated successfully, but these errors were encountered:
What happened: We are running on Dremio Enterprise v20.2.3. We use Snowflake ARP connector for Snowflake connectivity (dremio-snowflake-plugin-20.1.0.jar + snowflake-jdbc-3.13.5.jar) and use Snowflake Service Account to connect to those warehouse.
We have been notified by Snowflake team that every Snowflake Source in Dremio is creating sessions every 60 secs in Snowflake environment and we are trying to understand if this is the expected behavior. Note, these are not the Metadata refresh that Dremio does every 1 Hour for dataset discovery & dataset details fetch.
What you expected to happen: We would like to know if there is a way to stop this behavior. At this point am not sure if these sessions are consuming any Snowflake resources or not.
How to reproduce it (as minimally and precisely as possible): NA
Anything else we need to know?: Second part to this ticket is, Metadata refresh is essentially consuming Snowflake resources - Are there any ways to prevent it except increasing the Metadata Refresh frequency!
Details:
The text was updated successfully, but these errors were encountered: