-
Notifications
You must be signed in to change notification settings - Fork 4.1k
rttanalysis: if the trace is too large, round-trips will be missed #90961
Copy link
Copy link
Open
Labels
C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
Description
Is your feature request related to a problem? Please describe.
The rttanalysis framework relies on tracing to detect round-trips during execution of statements. This is problematic because traces can be truncated. See #90780.
Describe the solution you'd like
We might be able to leverage an RPC interceptor. Another thing we could potentially leverage is the logging library. A final alternative would be to inject into tracing to suppress truncation. A problem with suppressing truncation is that the traces could get large to the point of OOMing the process.
Jira issue: CRDB-21044
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
C-enhancementSolution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)