Managing sessions and queries

[jseldess]

• Add 1.1 page for SHOW SESSIONS
• Add 1.1 page for SHOW QUERIES
• Add 1.1 page for CANCEL QUERY
• Add 1.1 page for Managing Long-Running Queries
• Generate sql diagrams
• Add statements to 1.1 sidenav
• Add statements to 1.1 sql statements overview
• Update Query Behavior Troubleshooting page

Fixes #1562
Fixes #1572
Fixes #1571

[cockroach-teamcity]

This change is 

[jseldess]

cc: @knz, @dianasaur323, and @nstewart, if you want to take a look as well.

[dianasaur323]

Great, thank you. This is on my list of features to QA, so I'll let you know if I hit any issues.

[jseldess]

Actually, @nstewart and @dianasaur323, please hold off on your reviews until @itsbilal gets his in. Want to ensure everything's correct technically. Also need to integrate some changes from cockroachdb/cockroach#17579.

[itsbilal]

Looks good! Save for the last_active_query field in SHOW SESSIONS (as you pointed out).

You may also wanna mention that you can do queries like:

CANCEL QUERY (SELECT query_id FROM [SHOW CLUSTER QUERIES] WHERE client_address = '192.168.0.72:56194'
          AND username = 'mroach'
          AND query = 'SELECT * FROM test.kv ORDER BY k'); 

Instead of running the SELECT/SHOW first and then copy/pasting the ID into the CANCEL statement.

[jseldess]

TFTR, @itsbilal. Just expanded the SHOW SESSIONS to cover last_active_query. Please take a quick look.

I can't quite understand your suggestion about filtering above. I think part of your query got truncated?

[itsbilal]

@jseldess The initial message got truncated but I edited it. Take another look? It's basically just the nesting of a SELECT inside the CANCEL QUERY.

LGTM otherwise. It's your call on whether to mention the nested query example in the docs or not, but I'd argue it's a very useful one to have in there.

[jseldess]

Added your nested query example, @itsbilal. Thanks! Also added a dummy SHOW JOBS page to fix broken links. Will tackle that page in a follow-up PR.

[jseldess]

@nstewart, @dianasaur323, PTAL when you have time.

[jseldess]

Ping, @nstewart.

[jseldess]

@itsbilal, I ended up expanding this PR to cover CANCEL QUERY and another high-level page on Managing Long-Running Queries that links the disparate SQL statements. PTAL.

[jseldess]

Might need to integrate changes from cockroachdb/cockroach#17739.

[itsbilal]

When the cancelled query is part of a multi-statement transaction, CockroachDB aborts the transaction and sends a query execution cancelled error to the client, at which point the client should issue a ROLLBACK statement.

This seems to imply that CANCEL QUERY only works for queries in multi-statement transactions, and that it won't do anything for autocommit queries. It would be good to mention that it does cancel standalone/autocommit queries too. However cancellation isn't guaranteed; if the request is received too late, the query could still run till completion. That should probably be stated too.

Also note that the spelling of cancelled in the query execution cancelled error has been changed to canceled in cockroachdb/cockroach#17739 .

[jseldess]

Thanks, @itsbilal. Made updates.

[cockroach-teamcity]

http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/93b5eb769c385d245e17be210e63ad5073f0ebf9/

[dianasaur323]

I already ran through the docs, and things worked fine for me. Thanks Jesse.

On Mon, Aug 21, 2017 at 10:30 AM Jesse Seldess ***@***.***> wrote: Ping, @nstewart <https://github.com/nstewart>. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1828 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFgDWI_Su9imvGNqVglBPh381RWdHo42ks5saZRpgaJpZM4O5TI3> .

-- Diana Hsieh [email protected] 407-690-9048