ODBC Connection Does Not Disconnect

[bradleyjamrozik]

I have an on-premises Power BI Report Server that uses the Simba Spark ODBC Driver (2.8) to connect to Databricks. It can connect to a serverless warehouse successfully and run its queries, but it never seems to disconnect the session, and so the warehouse never registers as "idle" and auto-terminates. Has anyone seen this before? Any suggestions/recommendations? Thanks.

[Kaniz_Fatma]

Hi @bradleyjamrozik, It sounds like you’re encountering an issue with the Simba Spark ODBC Driver not properly disconnecting sessions when connecting to Databricks.

Let’s explore some potential solutions:

1. Check Connection Configuration:

   • Ensure that the ODBC connection configuration is correctly set up. You might want to review the connection settings, including the hostname, port, and authentication details.
   • If you’re using a proxy, make sure it’s configured properly. You can configure the Simba ODBC driver with a proxy in Windows by following these steps:
     • Open the ODBC Data Sources application.
     • Click the “System DSN” tab.
     • Select the Simba Spark ODBC Driver and click “Configure.”
     • Enter the connection information for your Apache Spark server.
     • Click “Advanced Options” and enable the “Driver Config Take Precedence” checkbox.
     • Click “OK” to save the changes¹.

2. Access Tokens and Authentication:

   • If you’re using access tokens for authentication, ensure that they are correctly generated and provided in the connection string. Access tokens can expire, so make sure you’re using valid tokens.
   • For example, when using the Simba Spark ODBC Driver, you can provide an access token in the connecti...

     Driver=Hortonworks Spark ODBC Driver;
     Host=server_host;
     Port=10000;
     SparkServerType=2;
     Schema=Spark_database;
     AuthMech=11;
     Auth_Flow=0;
     Auth_AccessToken=access_token;
     ThriftTransport=2;
     

     Replace access_token with your actual token².

3. SSL and HTTPS Options:

   • Verify that your HTTPS options and SSL settings are correctly configured. If you’re connecting to Databricks, check the following:
     • HTTPS Option: Obtain the HTTP Path from your Databricks connection details.
     • SSL Options: Ensure that the “Enable SSL” and “Use System Trust Store” options are checked³.

4. Session Management:

   • Some ODBC drivers allow you to configure session management settings. Check if there are any specific settings related to session timeouts or idle session handling.
   • You might need to adjust these settings to ensure that sessions are properly closed after executing queries.

5. Driver and Databricks Compatibility:

   • Verify that your Simba Spark ODBC Driver version (2.8) is compatible with the Databricks version you’re using. Sometimes compatibility issues can lead to unexpected behavior.
   • Consider updating the ODBC driver to the latest version if possible.

6. Logging and Debugging:

   • Enable logging for the ODBC driver to capture any relevant information during connection and query execution. Review the logs for any clues about why sessions are not disconnecting as expected.

Hopefully, one of these suggestions will help resolve the session disconnection problem! 😊🚀⁴⁵

^{To ensure we provide you with the best support, could you please take a moment to review the response and choose the one that best answers your question? Your feedback not only helps us assist you better but also benefits other community members who may have similar questions in the future.}

^{If you found the answer helpful, consider giving it a kudo. If the response fully addresses your question, please mark it as the accepted solution. This will help us close the thread and ensure your question is resolved.}

^{We appreciate your participation and are here to assist you further if you need it!}

[bradleyjamrozik]

Enabling "Driver Config Take Precedence" seems to be doing something. I'm going to monitor and report back.

[bradleyjamrozik]

It's working sometimes. Only correlation I have found so far is that a successful query will disconnect as expected but any error will keep the connection to the warehouse open indefinitely.