When Qlik Data Gateway Direct Access is implemented, sometimes as the workload increases post-implementation, customers may experience general stability issues. We suggest a basic health check to address the more well-known problems and stabilize your gateway implementation.
This article outlines three
- Verify the number of disconnects
- Verify the number of ODBC connector crashes
- Verify long-running metadata requests
Resolution
(1) Verify the number of disconnects
A high number of disconnects can cause reload disruptions. Some important disconnects will be recorded in the DirectAccessAgent logs. While a low volume of disconnects is expected and will typically recover within a few seconds, a high number of entries in the logs are indicative of a problem.
We suggest initiating an internal investigation if more than ten disconnects are found per day.
Search for “[ERROR] Connection to”, sample:
[Service ] [ERROR] Connection to <mytenant>.us.qlikcloud.com:443 failed
If the amount of disconnections is high, we suggest to refer to articles:
(2) Verify the number of ODBC connector crashes
ODBC connector crashes can impact concurrent reloads if Process Isolation is not enabled. We suggest customers who experience crashes in their logs enable Process Isolation and configure Dump file creation.
Process isolation for ODBC connector can be confirmed in the C:\ProgramData\Qlik\Gateway\configuration.properties. ODBC_PROCESS_ISOLATION_MODE, will be set to None if disabled, and set to Load if enabled.
It can also be verified using the logs. The ODBC logs named odbc-connector_logs.txt, odbc-connector_logs.txt.1 from 1 to n. If isolation is enabled, the files includes a port number, for example odbc-connector_logs_49156.txt where 49156 would represent a port number.
To identify whether there are crashes or not in your DAG (Direct Access Gateway) and proceed to enable Process Isolation we suggest reviewing Qlik Data Gateway - Direct Access - ODBC Crashes.
(3) Verify long-running metadata requests
Other cause of issues would be due to misconfiguration of third-party drivers, the details are outlined in Qlik Data Gateway Direct Access Data Preview long metadata requests.
Keep in mind that these recommendations are additional validations to the Best Practices and System Prerequisites documented in our Help Site:
Cause
Best Practices and System Requirements may not have been fully met.
Environment
- Qlik Data Gateway Direct Access
