kv: ensure all errors are recorded in always-on trace #55595
Labels
A-kv-observability
A-tracing
Relating to tracing in CockroachDB.
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-kv
KV Team
Projects
Errors should always be part of the recorded always-on trace. In particular,
*roachpb.Error
is trace metadata.We will need to decide who is in charge of adding errors to the trace at the DistSender->KVServer boundary (either way will work).
There are various other internal errors that can be "retried away"; these also need to be added to the trace. A classic example of that is a transaction refresh, which is terminated in the TxnCoordSender.
Jira issue: CRDB-3654
The text was updated successfully, but these errors were encountered: