Resolving Common Issues

The Resolving Common Issues page describes how to resolve the following common issues:

Troubleshooting Cluster Setup and Configuration

Note any errors - Make a note of any error you see, or check the logs for errors you might have missed.
If SQream DB can’t start, start SQream DB on a new storage cluster, with default settings. If it still can’t start, there could be a driver or hardware issue. Contact SQream support.
Reproduce the issue with a standalone SQream DB - starting up a temporary, standalone SQream DB can isolate the issue to a configuration issue, network issue, or similar.
Reproduce on a minimal example - Start a standalone SQream DB on a clean storage cluster and try to replicate the issue if possible.

Verify the correct login credentials - username, password, and database name.
Verify the host name and port
Try connecting directly to a SQream DB worker, rather than via the load balancer
Verify that the driver version you’re using is supported by the SQream DB version. Driver versions often get updated together with major SQream DB releases.
Try connecting directly with the built in SQL client. If you can connect with the local SQL client, check network availability and firewall settings.

Use SHOW_NODE_INFO to examine which building blocks consume time in a statement. If the query has finished, but the results are not yet materialized in the client, it could point to a problem in the application’s data buffering or a network throughput issue..
If a problem occurs through a 3^rd party client, try reproducing it directly with the built in SQL client. If the performance is better in the local client, it could point to a problem in the application or network connection.
Consult the Optimization and Best Practices guide to learn how to optimize queries and table structures.

Consult the SQL Statements and Syntax reference to verify if a statement or syntax behaves correctly. SQream DB may have some differences in behavior when compared to other databases.
If a problem occurs through a 3^rd party client, try reproducing it directly with the built in SQL client. If the problem still occurs, file an issue with SQream support.