diff --git a/v1.1/debug-and-error-logs.md b/v1.1/debug-and-error-logs.md index e990b31cb8a..98fd13612a1 100644 --- a/v1.1/debug-and-error-logs.md +++ b/v1.1/debug-and-error-logs.md @@ -16,8 +16,6 @@ As a command generates messages, CockroachDB uses the [command](#commands)'s [lo Each node's logs detail only the internal activity of that node without visibility into the behavior of other nodes in the cluster. When troubleshooting, this means that you must identify the node where the problem occurred or [collect the logs from all active nodes in your cluster](debug-zip.html). -{{site.data.alerts.callout_info}}You can also log queries your cluster receives.{{site.data.alerts.end}} - ### Commands All [`cockroach` commands](cockroach-commands.html) support logging. However, it's important to note: @@ -93,56 +91,6 @@ By default, commands besides `cockroach start` discard messages with the `INFO` The `--log-backtrace-at`, `--verbosity`, and `--v` flags are intended for internal debugging by CockroachDB contributors. -## Log Queries - -To help troubleshoot [query performance issues](query-behavior-troubleshooting.html#performance-issues), you can use [cluster-wide settings](cluster-settings.html) to enable logging for long-running SQL transactions or all queries, regardless of time. - -{{site.data.alerts.callout_danger}}These settings makes all queries slower and causes nodes to consume more memory. You should disable query logging as soon as you're done troubleshooting the query's issues.{{site.data.alerts.end}} - -### Enable Query Logging - -- **Long-running transactions**: - - ~~~ sql - > SET CLUSTER SETTING sql.trace.txn.enable_threshold = '[time]'; - ~~~ - - The `[time]` parameter accepts common time specifiers, such as `100ms` or `2s`. - -- **All queries**: - - ~~~ sql - > SET CLUSTER SETTING sql.trace.log_statement_execute = true; - ~~~ - -### Details - -After you enable query logging, whenever nodes process SQL statements, they generate messages with an `INFO` [severity level](#severity-levels). - -By default, these messages will get [written to files](#write-to-file), but are ultimate handled by whatever logging behavior you set for [`cockroach start`](start-a-node.html#logging). - -### Improve Query Performance - -After finding which queries are slow, use [`EXPLAIN`](explain.html) to examine them. It's possible that the query is slow because it performs a full-table scan. In these cases, you can likely improve the query's performance by [adding an index](create-index.html). - -*(More guidance around query performance optimization forthcoming.)* - -### Disable Query Logging - -Once you're done troubleshooting, you should disable query logging to prevent it from unnecessarily consuming resources. - -- **Long-running transactions**: - - ~~~ sql - > SET CLUSTER SETTING sql.trace.txn.enable_threshold = '0s'; - ~~~ - -- **All queries**: - - ~~~ sql - > SET CLUSTER SETTING sql.trace.log_statement_execute = false; - ~~~ - ## See Also - [Troubleshooting Overview](troubleshooting-overview.html) diff --git a/v1.1/manage-long-running-queries.md b/v1.1/manage-long-running-queries.md new file mode 100644 index 00000000000..b268a8b355e --- /dev/null +++ b/v1.1/manage-long-running-queries.md @@ -0,0 +1,59 @@ +--- +title: Manage Long-Running Queries +summary: Learn how to identify and cancel long-running queries. +toc: false +--- + +This page shows you how to identify and, if necessary, cancel SQL queries that are taking longer than expected to process. + +{{site.data.alerts.callout_info}}Schema changes (statements beginning with ALTER) cannot currently be cancelled. However, to monitor the progress of schema changes, you can use SHOW JOBS.{{site.data.alerts.end}} + +
+ +## Identify Long-Running Queries + +Use the [`SHOW QUERIES`](show-queries.html) statement to list details about currently active SQL queries, including each query's `start` timestamp: + +~~~ sql +> SHOW QUERIES; +~~~ + +~~~ ++----------------------------------+---------+----------+----------------------------------+-------------------------------------------+---------------------+------------------+-------------+-----------+ +| query_id | node_id | username | start | query | client_address | application_name | distributed | phase | ++----------------------------------+---------+----------+----------------------------------+-------------------------------------------+---------------------+------------------+-------------+-----------+ +| 14db657443230c3e0000000000000001 | 1 | root | 2017-08-16 18:00:50.675151+00:00 | UPSERT INTO test.kv(k, v) VALUES ($1, $2) | 192.168.12.56:54119 | test_app | false | executing | +| 14db657443b68c7d0000000000000001 | 1 | root | 2017-08-16 18:00:50.684818+00:00 | UPSERT INTO test.kv(k, v) VALUES ($1, $2) | 192.168.12.56:54123 | test_app | false | executing | +| 14db65744382c2340000000000000001 | 1 | root | 2017-08-16 18:00:50.681431+00:00 | UPSERT INTO test.kv(k, v) VALUES ($1, $2) | 192.168.12.56:54103 | test_app | false | executing | +| 14db657443c9dc660000000000000001 | 1 | root | 2017-08-16 18:00:50.686083+00:00 | SHOW CLUSTER QUERIES | 192.168.12.56:54108 | | NULL | preparing | +| 14db657443e30a850000000000000003 | 3 | root | 2017-08-16 18:00:50.68774+00:00 | UPSERT INTO test.kv(k, v) VALUES ($1, $2) | 192.168.12.58:54118 | test_app | false | executing | +| 14db6574439f477d0000000000000003 | 3 | root | 2017-08-16 18:00:50.6833+00:00 | UPSERT INTO test.kv(k, v) VALUES ($1, $2) | 192.168.12.58:54122 | test_app | false | executing | +| 14db6574435817d20000000000000002 | 2 | root | 2017-08-16 18:00:50.678629+00:00 | UPSERT INTO test.kv(k, v) VALUES ($1, $2) | 192.168.12.57:54121 | test_app | false | executing | +| 14db6574433c621f0000000000000002 | 2 | root | 2017-08-16 18:00:50.676813+00:00 | UPSERT INTO test.kv(k, v) VALUES ($1, $2) | 192.168.12.57:54124 | test_app | false | executing | +| 14db6574436f71d50000000000000002 | 2 | root | 2017-08-16 18:00:50.680165+00:00 | UPSERT INTO test.kv(k, v) VALUES ($1, $2) | 192.168.12.57:54117 | test_app | false | executing | ++----------------------------------+---------+----------+----------------------------------+-------------------------------------------+---------------------+------------------+-------------+-----------+ +(9 rows) +~~~ + +## Cancel Long-Running Queries + +Once you've identified a long-running query via [`SHOW QUERIES`](show-queries.html), note the `query_id` and use it with the [`CANCEL QUERY`](cancel-query.html) statement: + +~~~ sql +> CANCEL QUERY '14dacc1f9a781e3d0000000000000001'; +~~~ + +When the cancelled query is part of a multi-statement [transaction](transaction.html), CockroachDB aborts the transaction and sends a `query execution cancelled` error to the client, at which point the client should issue a [`ROLLBACK`](rollack-transaction.html) statement. + +## Improve Query Performance + +After cancelling a long-running query, use the [`EXPLAIN`](explain.html) statement to examine it. It's possible that the query was slow because it performs a full-table scan. In these cases, you can likely improve the query's performance by [adding an index](create-index.html). + +*(More guidance around query performance optimization forthcoming.)* + +## See Also + +- [`SHOW QUERIES`](show-queries.html) +- [`CANCEL QUERY`](cancel-query.html) +- [`EXPLAIN`](explain.html) +- [Query Behavior Troubleshooting](query-behavior-troubleshooting.html) diff --git a/v1.1/query-behavior-troubleshooting.md b/v1.1/query-behavior-troubleshooting.md index 35f6ed8795d..5685e05fad9 100644 --- a/v1.1/query-behavior-troubleshooting.md +++ b/v1.1/query-behavior-troubleshooting.md @@ -1,6 +1,6 @@ --- title: Query Behavior Troubleshooting -summary: Learn how to troubleshoot issues with specific queries with CockroachDB +summary: Learn how to troubleshoot issues with specific queries with CockroachDB toc: false --- @@ -14,15 +14,15 @@ If your queries return unexpected results, there are several possibilities: - You’ve encountered a [known limitation](https://github.com/cockroachdb/cockroach/issues?q=is%3Aopen+is%3Aissue+label%3Aknown-limitation), [UX surprise](https://github.com/cockroachdb/cockroach/issues?utf8=%E2%9C%93&q=is%3Aopen%20is%3Aissue%20label%3Aux-surprise) or other problem with [SQL semantics](https://github.com/cockroachdb/cockroach/issues?utf8=%E2%9C%93&q=is%3Aopen%20is%3Aissue%20label%3Asql-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](support-resources.html). - - CockroachDB has a bug. Please [file an issue](file-an-issue.html). +- CockroachDB has a bug. Please [file an issue](file-an-issue.html). ## Performance Issues -If your queries take much longer than expected, there are a few things you can check into: +If queries are taking longer than expected to process, 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. -- [Log and debug long-running queries/transactions](debug-and-error-logs.html#log-queries). +- [Identify and cancel long-running queries](manage-long-running-queries.html). If you're still unable to determine why the query executes slowly, please [file an issue](file-an-issue.html).