Open EasyVector opened 4 years ago
MULA Label Bot automatically applied the label database
to this issue, with a confidence of 1.00. Please mark this comment with :thumbsup: or :thumbsdown: to send your feedback!
MULA Label Bot automatically applied the label bug
to this issue, with a confidence of 1.00. Please mark this comment with :thumbsup: or :thumbsdown: to send your feedback!
MULA Label Bot automatically applied the label ui
to this issue, with a confidence of 1.00. Please mark this comment with :thumbsup: or :thumbsdown: to send your feedback!
MULA Label Bot automatically applied the label performance
to this issue, with a confidence of 0.92. Please mark this comment with :thumbsup: or :thumbsdown: to send your feedback!
MULA Label Bot is not confident enough to apply the label enhancement
to this issue, with a confidence of 0.03..
MULA Label Bot is not confident enough to apply the label client
to this issue, with a confidence of 0.01..
MULA Label Bot is not confident enough to apply the label question
to this issue, with a confidence of 0.01..
MULA Label Bot is not confident enough to apply the label document
to this issue, with a confidence of 0.00..
MULA Label Bot is not confident enough to apply the label server
to this issue, with a confidence of 0.00..
MULA Label Bot is not confident enough to apply the label design
to this issue, with a confidence of 0.00..
MULA Label Bot is not confident enough to apply the label security
to this issue, with a confidence of 0.00..
Describe the problem When troubleshooting a user's cluster, @vilterp and I observed that service latency appears to exclude distsql latency. To Reproduce Compare internal statement statistics (CRDB only) to the screenshot below.
Note that roughly 1/3 of the queries in the internal_statement_statistics table had latency >1s, yet the sql p99 latency graph shows latency of ~100ms, while the distsql p99 latency shows 10s+. Expected behavior I'd expect that the Service Latency: SQL 99th percentile graph would average all statements. Instead, it appears to exclude distSQL queries. Environment: v2.0.6