If a query returns an unexpected result or takes longer than expected to process, this page will help you troubleshoot the issue.
If your queries return unexpected results, there are several possibilities:
- You’ve encountered a known limitation, UX surprise or other problem with SQL semantics. Feel free to leave a comment on the existing issue indicating that you’ve encountered a problem as well.
- Your application has a bug. It's always worthwhile to check and double-check your application’s logic before filing an issue. That said, you can always reach out for support.
- CockroachDB has a bug. Please file an issue.
If your queries take much longer than expected, there are a few things you can check into:
Review your deployment's monitoring. General network latency or partitioning events can affect query response times.
If you're still unable to determine why the query executes slowly, please file an issue.
bad connection &
If you receive a response of
bad connection or
closed, this normally indicates that the node you connected to died. You can check this by connecting to another node in the cluster and running
cockroach node status.
Once you find the downed node, you can check its logs (stored in
cockroach-data/logs by default).
Because this kind of behavior is entirely unexpected, you should file an issue.
If we do not have a solution here, you can try using our other support resources, including:
- CockroachDB Community Forum
- Chatting with our developers on Gitter (To open Gitter without leaving these docs, click Help in the lower-right corner of any page.)