sql: emit more tracing events from the stats cache #54035
Conversation
|
This change is |
There was a problem hiding this comment.
Reviewed 1 of 1 files at r1.
Reviewable status:complete! 1 of 0 LGTMs obtained (waiting on @RaduBerinde)
pkg/sql/stats/stats_cache.go, line 192 at r1 (raw file):
// We are in the process of grabbing stats for this table. Wait until // that is complete, at which point e.stats will be populated. log.VEventf(ctx, 1, "waiting for statistics for table %d", tableID)
So the difference here is that we're always logging somewhere, but the location depends on the verbosity?
pkg/sql/stats/stats_cache.go, line 309 at r1 (raw file):
log.VEventf(ctx, 1, "refreshing statistics for table %d", tableID) ctx, span := tracing.ForkCtxSpan(ctx, "refresh-table-stats") defer tracing.FinishSpan(span)
Will this wait to finish until the goroutine below finishes?
The stats cache has various "slow" paths (where we need to query the system table). These are currently only logged if verbosity is high. This change switches to `VEvent` in most cases, so that these are visible during tracing (including in statement diagnostics bundles). This will allow us to diagnose slow planning times, e.g. due to the stats cache getting full. Release justification: low-risk change to existing functionality, high potential benefit for debugging issues. Release note: None
Add a few more tracing events around the use of the optimizer. Release note: None
RaduBerinde
force-pushed
the
more-events-stats-cache
branch
from
2d41695
to
7ea3a55
Compare
There was a problem hiding this comment.
TFTR! Updated and added a small commit that adds a couple of more events in the planning code.
Reviewable status:
pkg/sql/stats/stats_cache.go, line 192 at r1 (raw file):
Previously, rytaft (Rebecca Taft) wrote…
So the difference here is that we're always logging somewhere, but the location depends on the verbosity?
VEvent generates a trace event if we are tracing, and also logs it if the verbosity is high. The previous code did not generate a trace event if verbosity was not set.
pkg/sql/stats/stats_cache.go, line 309 at r1 (raw file):
Previously, rytaft (Rebecca Taft) wrote…
Will this wait to finish until the goroutine below finishes?
Silly me, fixed. Nice catch! This didn't cause any failures because I don't think we ever have a span in the context currently, but I put it in just in case.
There was a problem hiding this comment.
Reviewed 1 of 1 files at r2, 1 of 1 files at r3.
Reviewable status:
|
bors r+ |
|
Build succeeded: |
The stats cache has various "slow" paths (where we need to query the
system table). These are currently only logged if verbosity is high.
This change switches to
VEventin most cases, so that these arevisible during tracing (including in statement diagnostics bundles).
This will allow us to diagnose slow planning times, e.g. due to the
stats cache getting full.
Release justification: low-risk change to existing functionality, high
potential benefit for debugging issues.
Release note: None